From:	spiner AT comp DOT vuw DOT ac DOT nz (Steve Piner)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP V2.01 Released
Date:	24 Oct 1996 21:12:42 GMT
Organization:	Dept. of Comp. Sci., Victoria Uni. of Wellington, New Zealand.
Lines:	27
Message-ID:	<54om4a$6b0@wnnews1.netlink.net.nz>
References:	<199610220911 DOT LAA06039 AT omega DOT di DOT unipi DOT it> <326CDE3A DOT 364C AT Mathematik DOT tu-chemnitz DOT de>
NNTP-Posting-Host:	depot.comp.vuw.ac.nz
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <326CDE3A DOT 364C AT Mathematik DOT tu-chemnitz DOT de>,
Robert Hoehne  <Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de> wrote:
: Giuseppe Attardi wrote:
: > Since I use a dynamic loader which does not work anymore in V2,
: > does V2 use a different binary format than V1 (a.out)?

: DJGPP uses already for a very long time the COFF object format. Not
: only since V2.

This is true, but not necessarily helpful.  gcc was never able to
auto-stubify COFF files in DJGPP 1.x.

If you link your programs like this
        gcc -o foo *.o
then you will get both a COFF file and an EXE file produced - which is
probably Giuseppe wants.

If you link your programs without the "-o foo" then (I think) you'll
get a.exe and a.out.  If you use "-o foo.exe" then you'll get foo.exe
only.

Steve
-- 
 ____ ____
/ __//___ \  Steve Piner - spiner AT comp DOT vuw DOT ac DOT nz
\__ \ |  _/-----------------------------------------------------
/___/ |_|    (yes, I know it's a BUAF, but it's *my* BUAF) :-)

- Raw text -