Date: Tue, 26 Jun 2001 12:40:04 -0400 Message-Id: <200106261640.MAA08088@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 To: eliz AT is DOT elta DOT co DOT il CC: djgpp-workers AT delorie DOT com In-reply-to: <9003-Tue26Jun2001174339+0300-eliz@is.elta.co.il> Subject: Re: gcc 3.0 released References: <9003-Mon25Jun2001214631+0300-eliz AT is DOT elta DOT co DOT il> <200106251854 DOT OAA29303 AT envy DOT delorie DOT com> <9743-Mon25Jun2001224912+0300-eliz AT is DOT elta DOT co DOT il> <200106251955 DOT PAA29910 AT envy DOT delorie DOT com> <9003-Tue26Jun2001174339+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 Precedence: bulk > 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? This is what I have: $ unzip -l gcc30b.zip | grep djl 1312 06-22-01 13:01 lib/gcc-lib/djgpp/3.0/djgpp-x.djl > 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 ;-) I agree, but we can't seem to agree on a way of doing that that solves those types of problems in every case. We can still work towards that solution, but I'd like to get something released last week.