From: Steve D. P. <mai...@st...> - 2001-07-23 21:40:13
|
> i experiment such problem. > i fix them by setting needed env var as follow > > #--------- cdev.bat ---------------- > set PATH=.;C:\gcc-2.95.3\bin;C:\gcc-2.95.3\lib\gcc-lib\mingw32\2.95.3-4 > set C_INCLUDE_PATH=C:\gcc-2.95.3\include;C:\gcc-2.95.3\include\g++-3 > set CPLUS_INCLUDE_PATH=%C_INCLUDE_PATH% > set LIBRARY_PATH=.;C:\gcc-2.95.3\lib; > set TMPDIR=C:/temp I have tried setting these additional environment variables (modified for my particular installation directory of course), with no further success. Something seems exceptionally fishy about all this. The previous version of MinGW I installed just a few short months ago required no environmental settings at all (even an entry in PATH was technically optional)... it seems strange that MinGW suddenly developed dependencies on 5 or 6 environmental variables during the switch to a single-bundle distribution. Also, other mailing list posts I have read through offer conflicting environmental variable opinions... some listing other variables you have left out (such as COMPILER_PATH), others claiming that you still need nothing other than PATH at all. I'm trying to finish up work with the MinGW FAQ that I've been doing over the past couple of weeks, and find it terribly embarrassing that even the person trying to document the thing can't get it installed cleanly. Has anyone else encountered strange problems with include file and library search paths, that ended up being explained by something external I might be overlooking? If this is any further of a clue, I tried running gcc -print-search-dirs from an NT command-prompt... and while the 'programs:' and 'libraries:' sections looked fine, the 'install:' portion had an incorrect Cygwin-style path that struck me as odd (see below). Perhaps this has nothing to do with anything, though. C:\>gcc -print-search-dirs install: /mingw/lib/gcc-lib/mingw32/2.95.3-4/ programs: c:/development/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-4/;<etc>.... ... |