From: Simon Richter <Simon.Richter@hogyros.de>
To: "Peter S. Mazinger" <ps.m@gmx.net>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: uclibc patches
Date: Mon, 28 Mar 2005 02:35:00 -0000 [thread overview]
Message-ID: <4246294D.2010704@hogyros.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0503261432200.10495-100000@lnx.bridge.intra>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
Hi,
Peter S. Mazinger schrieb:
>>I'm not sure *-*-linux-uclibc would be the right choice, as it suggests
>>running Linux with uclibc as your C library, which is something the
>>binutils need not care about. I could, however, see a case for
>>*-*-uclinux due to the ABI differences and the need for relocation
>>information in fully linked executables.
> Maybe for binutils it does not make sense, but for gcc (libstdc++)
> it will be needed.
I think it may be much better to teach gcc how to switch its standard
libraries easily, possibly removing the fixincludes step from the
all-host target as a working gcc without system includes may be required
to bring the C library into a state where it can install its headers.
Simon
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 375 bytes --]
prev parent reply other threads:[~2005-03-27 3:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 2:21 Peter S. Mazinger
2005-03-20 17:16 ` Nick Clifton
2005-03-21 9:41 ` Mike Frysinger
2005-03-22 2:01 ` Christopher Faylor
2005-03-22 2:10 ` Mike Frysinger
2005-03-24 0:37 ` Nick Clifton
2005-03-20 20:24 ` Simon Richter
2005-03-27 17:55 ` Peter S. Mazinger
2005-03-28 2:35 ` Simon Richter [this message]
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=4246294D.2010704@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=ps.m@gmx.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).