Date: Fri, 29 Jun 2001 13:24:22 -0400
Message-Id: <200106291724.NAA23825@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: djgpp-workers AT delorie DOT com
In-reply-to: <3B3C5EDA.24973.3C891E@localhost> (snowball3@bigfoot.com)
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>
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
Precedence: bulk


> True, but the built-in hardcoded linker script is a fallback if it can't be 
> found in its path list. So if a linker script update is neccessary, a package 
> that updates the ones in lib/ldscripts will do the job.

On other OS's, the builtin script is the only one ever used.  There's
no reason why we can't do that either, if we're reasonably sure we
won't need to upgrade often.

I think saying "gcc version X requires binutils version Y" is a
reasonable solution to that problem.