delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2001/06/08/09:24:48

Date: Fri, 08 Jun 2001 14:51:27 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: Waldemar Schultz <schultz AT ma DOT tum DOT de>
Message-Id: <1858-Fri08Jun2001145127+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: djgpp AT delorie DOT com
In-reply-to: <3B20A3C4.5F245A4A@ma.tum.de> (message from Waldemar Schultz on
Fri, 08 Jun 2001 12:07:00 +0200)
Subject: Re: long line with make & gcc
References: <3B20A3C4 DOT 5F245A4A AT ma DOT tum DOT de>
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

> From: Waldemar Schultz <schultz AT ma DOT tum DOT de>
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 08 Jun 2001 12:07:00 +0200
> 
> I have a makefile that passes a long (some 300 characters) command line
> to gcc in the linking stage. This worked fine for many years.
> But since today the command line is truncated at character #124!
> Any Idea what could be the reason? I am stuck!
> I tried an earlier version of DJGPP but the same effect.
> 
> the following actually is _one_ long line:
> gcc -o ../bin/gsim.exe sim.o glb_lib.o sim_lib.o sys_lib.o
> tpg_lib.o fil_lib.o bgi_lib.o geo_lib.o e01_lib.o mdl_lib.o 
> Mdl00hy.o MDl01e.o MDL02t.o mdl03u.o mdl04bc.o mdl05p.o mdl06n.o
> ^^^^
> mdl07si.o mdl08ak.o mdl09ag.o mdl10z.o mdl11f.o mdl12bo.o mdl13ss.o
> mdl14do.o mdl15r.o mdl16sm.o mdl17os.o mdl18ci.o -lm -lp2c -lgrx20 -g
> gcc.exe: Mdl0: No such file or directory (ENOENT)
>          ^^^^

Does this long command work if you put it on a separate Makefile which
doesn't have anything but this line?

Are you sure your make.exe is indeed the DJGPP port of Make 3.79.1?
Are you sure your gcc.exe is indeed a DJGPP port of GCC?

I don't see anything special on the first glance, neither in your
Makefile nor in the environment.  So if the above doesn't help, I'd
suggest to build a Make executable with debug info, after inserting
the contents of system.c and dosexec.c from djlsr203.zip into one of
the Make source files, and then run Make under a debugger and see
what's going on inside `system' and `dosexec'.

- Raw text -


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