X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Mon, 10 Dec 2001 14:39:25 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
cc: djgpp-workers AT delorie DOT com
Subject: Re: v2.03 refresh ready for review/testing
In-Reply-To: <000001c18170$6f7eb660$443276d5@pandora.be>
Message-ID: <Pine.SUN.3.91.1011210143554.22674A-100000@is>
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 Mon, 10 Dec 2001, Tim Van Holder wrote:

> 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.