Dev C++ compiler reading Window sys variables

[Troy Seman]

I'm working with a basic "Hello World" program...

include <stdio.h>

int main(void)
{
printf("Hello World.");
}

...

I get the following compiler log...

Compiler: Default compiler
Executing g++.exe...
g++.exe "C:\Documents and Settings\supervisor\Desktop\test.cpp" -o "C:\Documents and Settings\supervisor\Desktop\test.exe" -I"C:\Apps\Dev-Cpp\lib\gcc\mingw32\3.4.2\include" -I"C:\Apps\Dev-Cpp\include\c++\3.4.2\backward" -I"C:\Apps\Dev-Cpp\include\c++\3.4.2\mingw32" -I"C:\Apps\Dev-Cpp\include\c++\3.4.2" -I"C:\Apps\Dev-Cpp\include" -L"C:\Apps\Dev-Cpp\lib"
C:/Apps/g95/lib/crt2.o(.text+0x16a):crt1.c: undefined reference to `__cpu_features_init'
collect2: ld returned 1 exit status

Execution terminated

...

The C:/Apps/g95 directory is an install of Fortran. This path should be unknown to Dev C++. This path occurs in the windows environmental variable "LIBRARY_PATH" and is necessary for a command line Fortran Compiler. If I remove this variable and restart Dev C++ the program will compile just fine. If I leave this variable in place, open a command line window and compile the program using g++ or gcc from the Dev C++ install directory, the program will compile just fine.

I've poured over the verious options and settings in Dev C++ but cannot find anything that will direct, or rather undirect Dev C++ from using system variables (Path statements). How do I stop this behavior? Keep in mind that I need these variables in place for other programs.

The workaround would be to start Dev C++ and a fortran command line window with alternate batch files that will set and destroy this LIBRARY_PATH variable on the fly. I'd like to avoid doing this because it's messy and I may have further problems down the road with system variables from other programs so I would like to understand/solve this problem from within Dev C++.

Thank you.

[laxman varada]

hi,

The workaround would be to start Dev C++ and a fortran command line window
with alternate batch files that will set and destroy this LIBRARY_PATH
variable on the fly. I'd like to avoid doing this because it's messy and I may
have further problems down the road with system variables from other programs.
I would like to how can i solve this prob with dev++c

regards,
phe9oxis,
http://www.guidebuddha.com