Date: Tue, 26 Jun 2001 20:24:52 +0300 (WET) From: Andris Pavenis To: Eli Zaretskii Cc: djgpp-workers AT delorie DOT com Subject: Re: gcc 3.0 released In-Reply-To: <9003-Tue26Jun2001174339+0300-eliz@is.elta.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Tue, 26 Jun 2001, Eli Zaretskii wrote: > > Date: Mon, 25 Jun 2001 15:55:30 -0400 > > From: DJ Delorie > > > > Ok, I guess I get to step in and decide then. Here's the question: > > > > I have a set of zips configured with a custom djl file with a unique > > name. If I put those on Simtel, will the average user have problems? > > Sorry, I'm confused: what does ``custom djl file'' mean? Are you > talking about the solution suggested by Andris, that is, to put a > linker script under lib/gcc-lib/, or something else? If the latter, > where will that file live, and what will be its name? > > In general, I'd like to avoid to have two or more linker script in > different places. We've had this with specs before, and I'm still > healing the wounds ;-) True, we had similar problems with specs earlier (and also djgpp.djl) beginning from gcc-2.8.1. At that time both files had IDENTICAL NAMES and that was source of all wounds (how to tell gcc to choose correct one, it was wery easy to get incorrect one by installation error for example unzip archives in wrong order) My earlier experience was reason to change the name and put it into gcc version specific directory of file when I put it into gcc-3.0 distribution for DJGPP. I remeber these problems and I would like to avoid that. I still believe it step in that direction to avoid similar problems with gcc-3.0 But it only a temporary solution. Linker scripts in djdev and gcc archives must disappear some time after they will be fixed in binutils Andris