From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>, "Jay Carlson" <nop@nop.com>
Cc: <linux-mips@fnet.fr>, <linux-mips@oss.sgi.com>
Subject: Re: stable binutils, gcc, glibc ...
Date: Sat, 14 Oct 2000 12:22:05 -0400 [thread overview]
Message-ID: <005601c035fa$e4b13a10$0701010a@ltc.com> (raw)
In-Reply-To: 20001014181257.C6499@bacchus.dhis.org
----- Original Message -----
From: "Ralf Baechle" <ralf@oss.sgi.com>
To: "Jay Carlson" <nop@nop.com>
Cc: "Jay Carlson" <nop@place.org>; <linux-mips@fnet.fr>;
<linux-mips@oss.sgi.com>
Sent: Saturday, October 14, 2000 12:12 PM
Subject: Re: stable binutils, gcc, glibc ...
> On Sat, Oct 14, 2000 at 12:11:39PM -0400, Jay Carlson wrote:
>
> > > Actually I'm trying to kill this entire naming problem by getting all
> > > patches back to the respective maintainers. Result: no pending
patches
> > > for cvs binutils, only tiny ones for glibc-current and egcs-current.
> >
> > What's going to happen to glibc 2.0.6? I suspect the embedded people
are
> > going to be stuck using it until we figure out how to trim down the
binary
> > size of 2.2.
>
> Which why I guess we still have to maintain it for a while or even come
> up with some alternative small libc.
I am fine with using 2.0.6 for a long time, at least until some markedly
superior option is available.
Regards,
Brad
WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Ralf Baechle <ralf@oss.sgi.com>, Jay Carlson <nop@nop.com>
Cc: linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: stable binutils, gcc, glibc ...
Date: Sat, 14 Oct 2000 12:22:05 -0400 [thread overview]
Message-ID: <005601c035fa$e4b13a10$0701010a@ltc.com> (raw)
Message-ID: <20001014162205.hhYddBiFHGVjelrpTaKhoX6_x3lMHYSeoKMWwCIZFpo@z> (raw)
In-Reply-To: 20001014181257.C6499@bacchus.dhis.org
----- Original Message -----
From: "Ralf Baechle" <ralf@oss.sgi.com>
To: "Jay Carlson" <nop@nop.com>
Cc: "Jay Carlson" <nop@place.org>; <linux-mips@fnet.fr>;
<linux-mips@oss.sgi.com>
Sent: Saturday, October 14, 2000 12:12 PM
Subject: Re: stable binutils, gcc, glibc ...
> On Sat, Oct 14, 2000 at 12:11:39PM -0400, Jay Carlson wrote:
>
> > > Actually I'm trying to kill this entire naming problem by getting all
> > > patches back to the respective maintainers. Result: no pending
patches
> > > for cvs binutils, only tiny ones for glibc-current and egcs-current.
> >
> > What's going to happen to glibc 2.0.6? I suspect the embedded people
are
> > going to be stuck using it until we figure out how to trim down the
binary
> > size of 2.2.
>
> Which why I guess we still have to maintain it for a while or even come
> up with some alternative small libc.
I am fine with using 2.0.6 for a long time, at least until some markedly
superior option is available.
Regards,
Brad
next prev parent reply other threads:[~2000-10-14 16:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-14 5:13 stable binutils, gcc, glibc Jun Sun
2000-10-14 3:55 ` Ralf Baechle
2000-10-14 4:21 ` Ralf Baechle
2000-10-14 10:57 ` Florian Lohoff
2000-10-14 14:51 ` Jay Carlson
2000-10-14 14:51 ` Jay Carlson
2000-10-14 15:09 ` Ralf Baechle
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:29 ` Bradley D. LaRonde
2000-10-14 16:29 ` Bradley D. LaRonde
2000-10-16 0:35 ` Ralf Baechle
2000-10-16 1:33 ` Mike Klar
2000-10-16 1:33 ` Mike Klar
2000-10-16 11:26 ` Jay Carlson
2000-10-16 11:26 ` Jay Carlson
2000-10-16 11:30 ` Ralf Baechle
2000-10-16 12:00 ` Ralf Baechle
2000-10-18 1:59 ` Jay Carlson
2000-10-18 1:59 ` Jay Carlson
2000-10-18 20:31 ` Ralf Baechle
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:11 ` Jay Carlson
2000-10-14 16:12 ` Ralf Baechle
2000-10-14 16:22 ` Bradley D. LaRonde [this message]
2000-10-14 16:22 ` Bradley D. LaRonde
2000-10-14 23:47 ` Keith Owens
2000-10-16 1:07 ` Ralf Baechle
2000-10-16 7:00 ` Alan Cox
2000-10-16 7:00 ` Alan Cox
2000-10-14 10:55 ` Florian Lohoff
2000-10-14 12:41 ` Ralf Baechle
[not found] ` <Pine.LNX.4.21.0010140730280.17430-100000@spawn.hockeyfiend.com>
2000-10-14 14:25 ` Ralf Baechle
2000-10-14 17:54 ` Florian Lohoff
2000-10-16 15:41 ` Maciej W. Rozycki
2000-10-18 4:04 ` The initial results (Re: " Jun Sun
2000-10-18 1:33 ` Florian Lohoff
2000-10-18 9:20 ` Jun Sun
2000-10-18 2:25 ` nick
2000-10-18 9:18 ` Florian Lohoff
2000-10-18 12:27 ` Ralf Baechle
2000-10-18 1:57 ` Ralf Baechle
2000-10-18 12:30 ` Florian Lohoff
2000-10-18 22:37 ` Ralf Baechle
2000-10-18 11:42 ` Geert Uytterhoeven
2000-10-18 17:15 ` Jun Sun
2000-10-20 14:55 ` Geert Uytterhoeven
2000-11-06 11:43 ` Jay Carlson
2000-11-06 11:43 ` Jay Carlson
2000-10-20 11:09 ` Andreas Jaeger
2000-10-20 12:03 ` Jay Carlson
2000-10-20 12:03 ` Jay Carlson
2000-10-21 1:24 ` Ralf Baechle
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='005601c035fa$e4b13a10$0701010a@ltc.com' \
--to=brad@ltc.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=nop@nop.com \
--cc=ralf@oss.sgi.com \
/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