Topic: Compiler failure-64 bit Vista --SOLVED--

[Shroudeye]

Hello Planet Descent! I am Shroudeye.

Okay, I got D3Edit AV40, locked and loaded.
D3SDK and EGCS 1.1.2 was also installed, and the enviroment variables were set...

But DALLAS refuses to work.

Here is my DALLAS output :
***
Virtual GCC Compiler layer for Descent 3
Copyright 1999 Outrage Entertainment
Source: "c:\d3-sdk_v14\osiris\egcstestlevel.cpp"
Output: "c:\d3-sdk_v14\osiris\egcstestlevel.dll"
DLLinit: "C:\d3-sdk_v14\osiris\dllinit.c"
Debug Info: None
Warning Level: 0
DLL Type: Level Script
Using gcc.exe found in C:\Compiler\egcs-1.1.2-mingw32\bin
gcc.exe: installation problem, cannot exec `cpp': No such file or directory
Error compiling "c:\d3-sdk_v14\osiris\egcstestlevel.cpp"
***
Also, my variable entries:
***
(User Entry)
Var. Name: GCC_EXEC_PREFIX
Var. Entry: C:\Compiler\egcs-1.1.2-mingw32\lib\gcc-lib
***
(System Entry)
Var. Name: Path
Var. Entry: <other entries>;C:\Compiler\egcs-1.1.2-mingw32\bin
***
Any ideas?

Thank you,
Shroudeye

[-<WillyP>-]

When you first open DALLAS for a new level you get that message about not finding the cpp, because there is no cpp until you write a script. Write and save a script, close DALLAS, then reopen it to see if DALLAS can find it.

Welcome to PD!

[Shroudeye]

Thanks WillyP...

I'm sorry, but its not it... DALLAS gives me this message WHEN I attempt to save the script...

I thought that I made a mistake when entering those variables, but all seems check, according to the tuts?

I'm using an 64-bit Vista, I suspect that's my problem, but I'm not sure?

[-<WillyP>-]

Darn, I was afraid you'd say that. You may be right about the 64 bit version of Vista being a problem but I am not sure.

What I do know is that the compiler runs under DOS rules and I and some others have had trouble caused by too long a path name. Try putting the compiler closer to root, something like this:

Code: [Select]

C:\egcs\lib\gcc-lib
My memory is a little hazy on the details but that is what I have on my machine. You might also try using a shorter level name. No more than 8.3 characters in the filename, ie; 12345678.123

[Shroudeye]

Nope...

I changed the name to "ctest", but to no avail :-(
***
Virtual GCC Compiler layer for Descent 3
Copyright 1999 Outrage Entertainment
Source: "c:\d3-sdk_v14\osiris\ctest.cpp"
Output: "c:\d3-sdk_v14\osiris\ctest.dll"
DLLinit: "C:\d3-sdk_v14\osiris\dllinit.c"
Debug Info: None
Warning Level: 0
DLL Type: Level Script
Using gcc.exe found in C:\Compiler\egcs-1.1.2-mingw32\bin
gcc.exe: installation problem, cannot exec `cpp': No such file or directory (--> WTH?!)
Error compiling "c:\d3-sdk_v14\osiris\ctest.cpp"
***

Edit: Ooops, I forgot relocating the compiler elsewhere, I'll try that Edit 2: NO EFFECT!

The diagnostics says that it can't find the file, but as I open up the D3SDK/osiris/, it IS there, along with the other, long named *.cpp's.

Any update(s) available for 64bit OS?

[-<WillyP>-]

Dang... there was some long discussion topics on .com about this. I can't remember all the details, sorry I am not much help but perhaps someone else remembers what worked for others... something about a slash, or other characters...

[Shroudeye]

Well; still thanks Will...

Anyone else knows anything?

[(LL)Atan]

Well I know it's is a pain.. you just want to go ahead but run into troubles. This is frustrating, I know.
So I'm not quite sure if this may help, but please read ahead:

6.5 Why does GCC say "cannot exec as"?

Q: When I try compiling a program, GCC aborts saying "Installation problem, cannot exec `as': No such file or directory (ENOENT)". What does that mean?

Q: When I try compiling a program, GCC aborts saying "Installation problem, cannot exec `cpp': No such file". Huh?

A: This usually means that GCC couldn't find some program it needs to run to compile your source. Check the COMPILER_PATH environment variable or what the COMPILER_PATH line in the DJGPP.ENV file says, and make sure they point to the directory where DJGPP programs reside. Also check that the named directory has all the required programs: cpp.exe, cc1.exe, cc1plus.exe, cxxfilt.exe, gasp.exe, as.exe, ld.exe, and (for Objective-C) cc1obj.exe. A typical case is when people fail to install the Binutils package and GCC cannot find as.exe (the assembler) and ld.exe (the linker). You can use the -v switch to GCC to see what programs it invokes and which one of them causes the fatal error.

Beginning with version 2.8.0 of GCC, the place where the pre-processor, cpp.exe, and the C and C++ compilers, cc1.exe and cc1plus.exe, are installed, has changed: they are no more in the same directory as gcc.exe itself. If you are using GCC version 2.8.0 or later, and the compiler cannot find cpp.exe or cc1plus.exe, read the installation instructions carefully: the file problems.txt explains how to change the settings on DJGPP.ENV so that GCC will find the pre-processor. Also, be sure to remove all traces of the previous compiler installation, since mixing different compiler versions can be another cause for such problems. See uninstalling a package.

[TechPro]

As a "result" of the long conversation thread on the old PD.com (that WillyP referred to) ... I had created a post on the Descent Guides Forum (http://www.prepare4descent.net/guidesforum/) regarding getting the compiler to work.  I had tried to keep it brief but to point out the things that HAVE to be certain ways.  Perhaps that can be of help.

Look here: http://www.prepare4descent.net/guidesforum/index.php?topic=126.0

[Shroudeye]

Thank you Atan and TechPro;

I found the problem, and it works! But... I feel a little shamed too, the problem was...um...I forgot those slashes at the end, so...

Anyways, looks like it works now. Thanks for all!