Date:	Sat, 30 Jun 2001 10:18:58 -0400
Message-Id:	<200106301418.KAA02560@envy.delorie.com>
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From:	DJ Delorie <dj AT delorie DOT com>
To:	eliz AT is DOT elta DOT co DOT il
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<3405-Sat30Jun2001083323+0300-eliz@is.elta.co.il>
Subject:	Re: gcc 3.0 released
References:	<008301c10050$1a8e4680$e33e1d18 AT nycap DOT rr DOT com> (matt AT conte DOT com) <3B3C5EDA DOT 24973 DOT 3C891E AT localhost> <200106291724 DOT NAA23825 AT envy DOT delorie DOT com> <925-Fri29Jun2001220308+0300-eliz AT is DOT elta DOT co DOT il> <200106291907 DOT PAA24825 AT envy DOT delorie DOT com> <3405-Sat30Jun2001083323+0300-eliz AT is DOT elta DOT co DOT il>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> That's true.  However, note that, unlinke GNU/Linux, our port is much
> less tested during development, and so more likely to suffer from
> bitrot.  We also release djdev much less frequently than glibc's
> release cycle.  For these two reasons, it's quite possible that we
> will need to change the script when GNU/Linux doesn't.

Linux uses a generic ELF file, so it's much more likely that the file
will have everything it needs, because it's shared among so many
systems.  Read the ELF script, make sure DJGPP has everything that
has, and we'll be in pretty good shape.

- Raw text -