This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc for windows



----- Original Message ----- From: "Sisyphus" <sisyphus1@optusnet.com.au>
.
.
Thanks for the link, NightStrike - it was worth a shot. (And, I might even have some success, yet, if I persevere.)

Seems to work ok if I:
1) also add x86_64-pc-mingw32\bin and libexec\gcc\x86_64-pc-mingw32\4.4.0 to the path;
2) set the CPATH environment variable to include both the x86_64-pc-mingw32\include and include folders;
3) set the LIBRARY_PATH environment variable to include the x86_64-pc-mingw32\lib, lib and lib\gcc\x86_64-pc-mingw32\4.4.0 folders.


I can then even compile C programs that need to link to the gmp and mpfr libraries (as supplied in mingw-w64-bin-gmp-mpfr.tar.bz2 , which is also available from http://sourceforge.net/project/showfiles.php?group_id=202880&package_id=245516&release_id=546049 ) .

This workaround (to what still has all the hallmarks of being the "Vista access problem") has probably always existed, but it's only in the last week or so that I found out about the CPATH and LIBRARY_PATH environment variables.

So it looks like I might have something to work with at last - though it's still early days, and I'm not yet ready to declare "problems solved".

Cheers,
Rob


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]