From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Ian Lance Taylor <iant@google.com>,
binutils@sourceware.org, gcc-patches@gcc.gnu.org,
gdb-patches@sourceware.org
Subject: Re: [patch ping] change linux-gnu* -> linux* in libtool files
Date: Mon, 25 Sep 2006 18:48:00 -0000 [thread overview]
Message-ID: <1159210072.24808.23.camel@localhost.localdomain> (raw)
In-Reply-To: <200609251359.17234.vapier@gentoo.org>
On Mon, 2006-09-25 at 13:59 -0400, Mike Frysinger wrote:
> On Monday 25 September 2006 13:29, Ian Lance Taylor wrote:
> > Mike Frysinger <vapier@gentoo.org> writes:
> > > ok to commit to sourceware repo ?
> > >
> > > upstream libtool changed libtool.m4 a while back to look for 'linux*)'
> > > instead of 'linux-gnu*)' ... ive also tweaked the ltconfig accordingly
> >
> > Um, why? The binutils and gdb are owned by and maintained on behalf
> > of the FSF. A few years ago the FSF requested that we go through and
> > change linux* to linux-gnu*, in accordance with the their preferred
> > name of GNU/Linux. That's not to say that your patch is automatically
> > rejected, but it certainly needs some motivation.
>
> this has nothing to do with ideological "Linux" versus "GNU/Linux" ... we went
> through this before with the fixing of all the configure targets in
> bfd/gas/ld/gcc/etc...
>
> linux-gnu implies glibc and glibc is not the only libc you can use out there
> with linux
Not to say you're wrong, but this is the first I've heard
that linux-gnu implies glibc. Is there someplace where this
is written?
next prev parent reply other threads:[~2006-09-25 18:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 17:14 Mike Frysinger
2006-09-25 17:30 ` Ian Lance Taylor
2006-09-25 17:59 ` Mike Frysinger
2006-09-25 18:48 ` Michael Snyder [this message]
2006-09-25 19:08 ` Mike Frysinger
2006-09-25 19:20 ` Michael Snyder
2006-09-25 19:32 ` Paul Brook
2006-09-25 19:41 ` Mike Frysinger
2006-09-25 19:37 ` Ian Lance Taylor
2006-09-25 21:22 ` Thiemo Seufer
2006-09-26 13:54 ` Nick Clifton
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=1159210072.24808.23.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=iant@google.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