From: Stephan Linz <linz@li-pro.net>
To: ptxdist@pengutronix.de
Subject: [ptxdist] OSELAS.Toolchain() rpatches and behaviors
Date: Thu, 08 Aug 2013 21:45:45 +0200 [thread overview]
Message-ID: <1375991145.2852.40.camel@keto> (raw)
Hi,
I'm working on eglibc support for the OSELAS.Toolchain() project. I need
the Embedded GLIBC for MicroBlaze toolchains. It is the default libc for
such target devices.
Where can I submit patches for the OSELAS.Toolchain() -- here on the
ptxdist mailing list?
Another question (please correct me when I'm wrong): As far as I know
the OSELAS.Toolchain() will not support multi-lib compilation for glibc.
Has anyone ever worked on such expansion? I need the multi-lib support
(mainly for eglibc) for the MicroBlaze toolchain.
--
Best regards,
Stephan Linz
______________________________________________________________________________
MB-Ref: http://www.li-pro.de/xilinx_mb:mbref:start
OpenDCC: http://www.li-pro.net/opendcc.phtml
PC/M: http://www.li-pro.net/pcm.phtml
Sourceforge: http://sourceforge.net/users/slz
Gitorious: https://gitorious.org/~slz
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2013-08-08 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 19:45 Stephan Linz [this message]
2013-08-16 13:08 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1375991145.2852.40.camel@keto \
--to=linz@li-pro.net \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox