X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f From: pavenis AT lanet DOT lv To: "Tim Van Holder" , Date: Thu, 27 Dec 2001 19:07:52 +0200 MIME-Version: 1.0 Subject: Re: Small issue with current gcc setup (djgpp-x.djl) Message-ID: <3C2B7188.24754.198286@localhost> In-reply-to: <000401c18a56$bae67310$ce3276d5@pandora.be> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body 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 21 Dec 2001 at 20:36, Tim Van Holder wrote: > I ran into an annoying problem with the gcc 3.02 packages: > > Because it is possible to have ld in gcc's private dir, I > had switched an ld-based link rule to use gcc: > > old: ld -X -S -r -T dlx.ld -o foo.o foo1.o foo1.o > new: gcc -Wl,-X,-S,-r -T dlx.ld -o foo.o foo1.o foo1.o > > Both should be functionally equivalent (except that the > second also runs stubify in our case and creates foo.exe, > but that can't be avoided, I suppose). > However, gcc3 unconditionally uses -T djgpp-x.djl in specs, > even if another -T option is given, and this causes foo.o > to be an executable instead of an object. > Using %{!T:-T djgpp-x.djl} in the specs fixes it. > After a small fix it's OK: %{!T*:-T djgpp-x.djl} (One can specify -Tfoo which is OK for gcc but is not catched by simply %{!T:....}) Andris > >