From: Nick Clifton <nickc@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: binutils@sources.redhat.com
Subject: Re: uclibc patches
Date: Thu, 24 Mar 2005 00:37:00 -0000 [thread overview]
Message-ID: <42418F83.3030901@redhat.com> (raw)
In-Reply-To: <200503211701.37726.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Hi Mike,
>>>basically every place you see '-linux-gnu*', add a similar
>>>'-linux-uclibc*' match
>>
>>Perhaps it is politically incorrect to suggest this, but wouldn't it
>>make sense to just allow -linux-* rather than add a bunch of
>>linux-uclibc's everywhere?
> it doesnt matter to me which is used so long as 'it works' :)
I like this idea. So I have checked in the attached variant of your
patch together with these ChangeLog entries:
bfd/ChangeLog
2005-03-23 Mike Frysinger <vapier@gentoo.org>
Nick Clifton <nickc@redhat.com>
* config.bfd: Accept any C library to accompany a GNU Linux
implementation, not just the GNU C library.
* configure.in: Likewise.
* configure: Regenerate.
gas/ChangeLog
2005-03-23 Mike Frysinger <vapier@gentoo.org>
Nick Clifton <nickc@redhat.com>
* configure.tgt: Accept any C library to accompany a GNU Linux
implementation, not just the GNU C library.
* configure.in: Likewise.
* configure: Regenerate.
ld/ChangeLog
2005-03-23 Mike Frysinger <vapier@gentoo.org>
Nick Clifton <nickc@redhat.com>
* configure.host: Accept any C library to accompany a GNU Linux
implementation, not just the GNU C library.
* configure.tgt: Likewise.
* emultempl/elf32.em: Likewise.
Cheers
Nick
[-- Attachment #2: anylibc.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 5031 bytes --]
next prev parent reply other threads:[~2005-03-23 15:34 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 [this message]
2005-03-20 20:24 ` Simon Richter
2005-03-27 17:55 ` Peter S. Mazinger
2005-03-28 2:35 ` Simon Richter
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=42418F83.3030901@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=vapier@gentoo.org \
/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).