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 19:31:34 +0100
Message-ID: <000001c181a8$e6560350$443276d5@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <Pine.SUN.3.91.1011210163947.23701A-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
Precedence: bulk

> > > 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.
> 
> It isn't needed only if you say "gcc -o foo.exe"

That's what I mean - if coff-go32 is the default forced by djgpp.djl,
then foo.exe above would also be raw COFF, unless stubify was run on
it.