Date: Wed, 19 Sep 2001 18:37:08 +0300 (WET) From: Andris Pavenis X-Sender: pavenis AT ieva06 To: CBFalconer Cc: djgpp AT delorie DOT com Subject: Re: GPC fails - why? In-Reply-To: <3BA89555.2D4FB0BF@yahoo.com.NOSPAM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Precedence: bulk On Wed, 19 Sep 2001, CBFalconer wrote: > (* POSTED and MAILED *) > > Hans-Bernhard Broeker wrote: > > > > CBFalconer wrote: > > > Just downloaded and installed GPC20bb, together with gcc2953b and > > > gpp2953b. I get the following on first trial: > > > > I suspect you have the wrong GPC package. Or some serious installation > > error in your general DJGPP setup. > > > > >>#include "..." search starts here: > > >>#include <...> search starts here: > > >> /usr/local/include > > >> JDIR/i586-pc-msdosdjgpp/include > > > > This is seriously damaged. Unless it got mashed in transport, you > > should try to find out what ate the "$D" that's missing at the front > > of that line. But see the end of this message, first. > > This is totally unclear to me. I don't know where a "$D" should > have come from or where is should be. I assume before the "JDIR", > but then I don't know what created that either? Getting string '$DJDIR' to survive in nested makes is not an easy thing. One can see that in sources of DJGPP port of gcc-2.95.3 (some time ago I "stole" an idea from sources of GPC ...). As I remember there were no smashed '$DJDIR' in my latest builds of GPC in May. I don't know whether the same modifications are done in binaries which were used in this case Fortunatelly we have get rid of this annoyance in gcc-3.0.X by using prefix=/dev/env/DJDIR > > > > I hope you didn't edit DJGPP.ENV, did you? > > No. Maybe it needs it. > > > > >> -o hello c:/djgpp/lib/crt0.o -Lc:/djgpp/lib/gcc-lib/djgpp/2.952 > > [...] > > >>gpc.exe: installation problem, cannot exec `-o': No such file or \ > > >> directory (ENOENT) > > > > This one's the real bugger. There should have been the full pathname > > of the linker program ('ld' or 'collect2' usually) at the beginning of > > that line, before the '-o hello'. > > > > > [1] c:\djgpp>dir /4 /s lib\gcc-lib\djgpp > > > > > Volume in drive C is W98SYSFAT32 Serial number is 39EB:49EB > > > Directory of C:\djgpp\lib\gcc-lib\djgpp\* > > > > > [.] [..] [2.952] > > > [2.953] > > > 0 bytes in 0 files and 4 dirs > > > > This smells of version mixup. You have directories from two different > > GCC releases sitting around. The contents of other directories > > confirms it: you've mixed GPC version 2.95.2 with GCC version 2.95.3. > > That's exactly the reason for your troubles, I think. > > I installed GCC first, and it worked in rhide. Then went looking > for GPC, which included the 2.95.2 stuff, and installed that. I > assumed it installed the library pieces it was compiled for. > rhide blew up using it, so I tried the command line. So it seems > to have nothing to do with rhide. > > No, I didn't edit DJGPP.ENV, but maybe it should be. Obviously > this GPC needs different libraries than GCC. Or where can I find > a more up to date GPC (this was GPC20bb.zip). > > BTW GCC still functions properly. It has not been fouled. > > I hope you do not mind the post and mail reply. I am anxious to > get this running. > Haven't messed with building GPC from sources for a rather long time (since May) so I cannot say much more Andris