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 19:20:00 -0000 [thread overview]
Message-ID: <1159212014.24808.35.camel@localhost.localdomain> (raw)
In-Reply-To: <200609251508.00560.vapier@gentoo.org>
On Mon, 2006-09-25 at 15:07 -0400, Mike Frysinger wrote:
> On Monday 25 September 2006 14:47, Michael Snyder wrote:
> > 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?
>
> common practice ? :)
Well... not so common that I've heard of it...
> in the uClibc world we use $arch-$vendor-linux-uclibc to keep things clean and
> sep from the host glibc toolchain $arch-$vendor-linux-gnu ... when we
> proposed adding support for *-linux-uclibc and *-linux-newlib and
> *-linux-dietlibc to binutils, the cleaner solution was to simply accept
> *-linux-* in configure files
That may be sound -- but uClibc is not the world. Who else is doing
something similar?
> upstream libtool changed their files a while ago to accept 'linux*)' rather
> than 'linux-gnu*)' ... so my patch isnt treading into new territory, it's
> backporting updates from upstream libtool
Cool -- but libtool, while widely used, is not the world either.
The world, in this context, is {fsf/gnu} or maybe {fsf/gnu/linux},
of which libtool is certainly a part -- but I'm not sure if we
traditionally 'backport' changes from libtool into binutils without
question.
next prev parent reply other threads:[~2006-09-25 19:20 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
2006-09-25 19:08 ` Mike Frysinger
2006-09-25 19:20 ` Michael Snyder [this message]
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=1159212014.24808.35.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