Message-ID: <3BD90AB8.590AE140@falconsoft.be>
Date: Fri, 26 Oct 2001 09:03:20 +0200
From: Tim Van Holder <tim DOT vanholder AT falconsoft DOT be>
Organization: Anubex (www.anubex.com)
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.16-3 i686)
X-Accept-Language: en, nl-BE, nl
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problem linking with gcc
References: <3BD8BDA4 DOT 5080408 AT earthlink DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 23
NNTP-Posting-Host: 194.78.64.238
X-Trace: 1004079934 reader1.news.skynet.be 36457 194.78.64.238
X-Complaints-To: abuse AT skynet DOT be
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Micah J. Kimbrough" wrote:
> 
> Hello,
>      I am trying to compile and link a program with gcc that came with
> djcpp. I tried entering the link command manually like gcc.exe -o
> file.exe file.o file.o file.o ... etc. -lm  and I modified the makefile
> to use gcc and ran it as well and it still will not link under Windows
> 98 dos shell. What it is seems to be doing is cutting off the link
> command even when running the make file. This is the error I get:
> gcc.exe: fil No such file or directory (ENOENT). Notice that file.o is
> fil, I meant to do that because it is cutting off the actual file name
> when I run make. I can add parameters to the makefile and manually and
> it cuts it off at a different place.

That's typical for DOS shells, such as command.com.
Do you have the DJGPP port of bash installed?  If so, add

  SHELL = /bin/sh

to the Makefile; then there should be no command-line length issues.
And of course you can just run bash and execute the compilation/link
from
the command line as well.