X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	"'Eli Zaretskii'" <eliz AT is DOT elta DOT co DOT il>
Cc:	<djgpp-workers AT delorie DOT com>
Subject:	Re: v2.03 refresh ready for review/testing
Date:	Mon, 10 Dec 2001 15:32:12 +0100
Message-ID:	<000201c18187$74ce9bf0$443276d5@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook, Build 10.0.2627
In-Reply-To:	<Pine.SUN.3.91.1011210143554.22674A-100000@is>
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2462.0000
Importance:	Normal
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

> > I thought that gcc (well, ld) used coff-go32-exe by default so that
> > the 'foo' created by 'gcc $(OBJECTS) -o foo' is an EXE file (just
> > without the extension) and not a raw COFF file...
> 
> Obviously, that doesn't happen.  IIRC, we don't invoke 
> go32-v2 except for 
> raw COFF.
> 
> I don't know enough about the GCC build process, but it's 
> quite possible 
> that "gcc -o foo" uses the linker script, and at least djgpp.djl says:
> 
>    OUTPUT_FORMAT("coff-go32")
> 
> which defeats ld's default.

Yes, but if that's true, stubify would still be needed, and I
thought that was not needed with recent versions of binutils/gcc.
All of ld's builtin scripts (execept .xr and .xu, but those are for
relocateable objects IIRC) use OUTPUT_FORMAT("coff-go32-exe").
So maybe djgpp.djl should also default to .exe?

- Raw text -