X-Authentication-Warning:	ieva01.lanet.lv: pavenis owned process doing -bs
Date:	Tue, 3 Aug 1999 09:56:39 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Laurynas Biveinis <lauras AT softhome DOT net>
cc:	DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject:	Re: GCC 2.95 and gperf
In-Reply-To:	<37A58883.3BDB59BC@softhome.net>
Message-ID:	<Pine.A41.4.05.9908030950270.38466-100000@ieva01.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 2 Aug 1999, Laurynas Biveinis wrote:

> Andris Pavenis wrote:
> > It's old version of gperf. You should apply patch included in gcc-2.95
> > sources (directory gcc-2.95/contrib)
> 
> It seems that post-2.7 gperf snapshot is required. Nobody has 
> ported it to DJGPP yet, but I somehow managed to compile it,
> then it worked. Also bison was required. After I installed
> bison, everything went successfully until making distribution
> zips. I don't have InfoZip's zip, so I just removed my old 
> EGCS-1.1.2 compiler and copied files from installation directory 
> to my DJGPP tree.
> 
> But after this my new compiler refuses to compile anything -
> it died with error "Load error: no DOS memory" or 
> cpp.exe: installation problem, cannot exec `c:/djgpp/bin/cpp.exe':
> Argument list
>  too long (E2BIG)
> I added "-v" switch, redirected output to file and it is 
> about 57 KB ! Is it OK to send such size file here?
> When looking to that file I noticed interesting thing:

You copied cpp.exe to $DJDIR/bin. It should cause no harm with current
CVS version of DJGPP, but will behave as You described with earlier
versions.

Cure:
remove definition of COMPILER_PATH from DJGPP.ENV (section gcc)
(or remove cpp.exe from $DJDIR/bin). 

I think it would be nice to to have cpp.exe (it's different from 
one gcc.exe is using) in $DJDIR/bin as preprocessor is needed for RSXNTDJ
AFAIK) but unfortunatelly that breaks earlier versions of DJGPP.

Andris

> -----
> Reading specs from c:/djgpp/lib/specs
> gcc version 2.95 19990728 (release)
>  c:/djgpp/bin/cpp.exe -lang-c -v -isystem c:/djgpp/bin/include
> -D__GNUC__=2 -D__
> GNUC_MINOR__=95 -Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2 -DDJGPP_MINOR=2
> -D__unix_
> _ -D__i386__ -D__GO32__ -D__MSDOS__ -D__DJGPP__=2 -D__DJGPP_MINOR__=2
> -D__unix -
> D__i386 -D__GO32 -D__MSDOS -D__DJGPP=2 -D__DJGPP_MINOR=2 test-c.c
> c:/djgpp/tmp\c
> cuY1ldC.i
> -----
> All OK, right? But after this it says:
> -----
> Reading specs from c:/djgpp/lib/specs
> gcc version 2.95 19990728 (release)
>  c:/djgpp/bin/cpp.exe -lang-c -v -isystem c:/djgpp/bin/include -Dunix
> -Di386 -DG
> O32 -DMSDOS -DDJGPP=2 -DDJGPP_MINOR=2 -D__unix__ -D__i386__ -D__GO32__
> -D__MSDOS
> __ -D__DJGPP__=2 -D__DJGPP_MINOR__=2 -D__unix -D__i386 -D__GO32
> -D__MSDOS -D__DJ
> GPP=2 -D__DJGPP_MINOR=2 -D__GNUC__=2 -D__GNUC_MINOR__=95 -Dunix -Di386
> -DGO32 -D
> MSDOS -DDJGPP=2 -DDJGPP_MINOR=2 -D__unix__ -D__i386__ -D__GO32__
> -D__MSDOS__ -D_
> _DJGPP__=2 -D__DJGPP_MINOR__=2 -D__unix -D__i386 -D__GO32 -D__MSDOS
> -D__DJGPP=2
> -D__DJGPP_MINOR=2 -isystem c:/djgpp/bin/include test-c.c -o
> c:/djgpp/tmp\ccuY1ld
> C.i
> -----
> 8-0 And it repeats all over again, and "-D..." list is 
> going longer and longer, and finally it exits
> with error message. What can cause this infinite
> recursion/loop? Why only cpp is called all the time?
> 
> Thanks for your help,
> Laurynas Biveinis
> 
> 

- Raw text -