From:	michael DOT mauch AT gmx DOT de (Michael Mauch)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Problem on command line gnumake, bash and other compilers
Date:	Mon, 08 Jun 1998 08:11:27 +0200
Organization:	Gerhard-Mercator-Universitaet -GH- Duisburg
Lines:	30
Message-ID:	<6lfva4$3bd$1@news-hrz.uni-duisburg.de>
References:	<357aff25 DOT 6270481 AT news DOT earthlink DOT net>
NNTP-Posting-Host:	ppp192.uni-duisburg.de
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Sun, 07 Jun 1998 21:05:35 GMT, medialinkdev AT earthlink DOT net (Chet
Simpson) wrote:

> First, I'm using bash as my shell under DOS and Win95.  I'm having a
> problem with the command line being sent to some executables being
> truncated at 130 characters, primarily when using a compiler other
> than gcc/djgpp.
[...]
> Are there any special shell flags or command line options I can send
> to bash in order to get around this problem?

No, you can't. DOS' command line length is limited to about 125
characters, and "normal" DOS programs won't see more than 125
characters. DJGPP-compiled programs use the DJGPP-way to get around this
limit, so that's why it works if you use only them. The Windows 95
console has another way to get around this problem, but only programs
that know about this way can use it. 

At present, DJGPP doesn't use the Windows 95-workaround for long command
lines, so DJGPP-compiled programs don't read long command lines given by
Windows 95 and they don't give long command lines in the Windows
95-style to other programs.

A question to the maintainers: are there any considerations to use both
the "!proxy" way and the Windows 95 "CMDLINE" way in DJGPP 2.02? I use
the DJGPP-compiled "make" all the time, but when it calls a Win32-gcc,
it's always trouble to get around that command line length limit.

Regards...
		Michael

- Raw text -