Date:	Mon, 19 Mar 2001 09:56:39 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Message-Id:	<200103190756.JAA21999@is.elta.co.il>
To:	djgpp AT delorie DOT com
In-reply-to:	<ygUr6.339$Xm3.43833@newshog.newsread.com> (nunya@business.com)
Subject:	Re: Run Error, need help!
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010313115137 DOT 10085B-100000 AT is> <ygUr6.339$Xm3 DOT 43833 AT newshog DOT newsread DOT com>
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: "CJ" <nunya AT business DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Thu, 15 Mar 2001 00:45:18 GMT
> 
> when I compile, it says no errors, when i go to link it says:
> 
> c:/djgpp/bin/ld.exe -o hello.exe
> c:/djgpp/lib/crt0.o -Lc:/djgpp/lib -Lc:/djgpp/lib/gcc-lib/djgpp/2.81 -Lc:/dj
> gpp/bin -Lc:/djgpp/lib hello.o -lstdcx -Tdjgpp.djl -lgcc -lc -lgcc
> c:/djgpp/bin/stubify.exe -v hello.exe
> The error was:  Invalid argument (EINVAL)
> no errors

We have identified the possible source if this problem.  It happens on
Windows ME when long file names support in DJGPP programs is
disabled.  To work around these problems, set LFN=y in the
environment.

The bug is actually on one of the library functions; it will be fixed
in the next version.  However, since there's no reason to disable LFN
on Windows ME, the problem is not so grave.

(I'm guessing that this hits people who use old versions of DJGPP
distributed on a CD with some books, where LFN was turned off by the
DJGPP.ENV file.  Note the old version of GCC printed in the
compilation trace above.)

- Raw text -