ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2009/01/28/19:56:46

X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Wed, 28 Jan 2009 19:56:26 -0500
Message-Id: <200901290056.n0T0uQO2010238@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to:
<98aac42e-1698-4f3c-a154-4a430c8d8a6e AT i18g2000prf DOT googlegroups DOT com>
(message from Jim Michaels on Wed, 28 Jan 2009 15:31:07 -0800 (PST))
Subject: Re: linking the hard way
References: <98aac42e-1698-4f3c-a154-4a430c8d8a6e AT i18g2000prf DOT googlegroups DOT com>
Errors-To: nobody AT delorie DOT com

> 1. will there be support for response files?

All djgpp apps support response files, and have for MANY years.  It's
built-in to the djgpp runtime.

	 gcc -O2 -o myprog.exe @files.lst

> 2. in order to make an executeable that I can use with exe2coff and
> cwsdstub.exe, I assume I need some sort of crt0.o, but I find several
> such as gcrt0.o and libc.a.  which one(s) do I link in and what are
> they for?

Just build your exe with gcc and you'll get the right things.

> I am getting a ton of undefined reference errors about things related
> to the C runtime and my own stuff.

Because you are using the linker directly.  Don't.  Use gcc to link;
it adds in all the things you need, automatically.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019