Date: Tue, 23 Oct 2001 08:48:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Micah J. Kimbrough" <sciencecenter AT earthlink DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: HELP!! Please!
In-Reply-To: <3BD478A5.80002@earthlink.net>
Message-ID: <Pine.SUN.3.91.1011023084746.9162B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 22 Oct 2001, Micah J. Kimbrough wrote:

> The last line I have does the linking. I have
> c:\djcpp\bin\ld.exe -o file.exe file.o file.o file.o ... etc.

Don't do that!  Invoking the linker directly like shown above will
produce an unworkable program (it will crash when you try to run it).

Instead, link with GCC, like this:

  gcc -o file.exe file.o file.o file.o ...

I believe the file README.1ST in the distribution explains this.

> I have noticed that is reads only half the line and ends 
> in errors. Is there a way to get it to read the whole line and finish 
> the linking?

If the command line is longer than 126 characters, command.com will
truncate it.  You can work around this by preparing a Makefile where
GCC is invoked directly (not through batch files), or by using a
response file.  For details, read section 16.4 of the DJGPP FAQ list.