Oliver Puetz wrote:
It seems not to work. I've made the settings like you wrote in my .cshrc setenv reports this:
GPC_EXEC_PREFIX=/net/sgi249/share/mips/gnu/lib/gcc-lib/mips-sgi-irix6.2/2.8.1/ CC_LIBRARY_PATH=/tmp/puetzobq/usr/local/lib/gcc-lib/mips-sgi-irix6.2/2.8.1/
[somehow the first character of the two variable names got lost. I assume they were there...]
Reading the docs and doing a "strings gpc" it turns out that the env variable name is wrong: it's still GCC_EXEC_PREFIX. Maybe this should be fixed or documented. And the libraries are searched at LIBRARY_PATH. The value for LIBRARY_PATH looks correct for me, but GCC_EXEC_PREFIX should be set to net/sgi249/share/mips/gnu/lib/gcc-lib/ in your case.
Try gpc -print-search-dirs to check if the settings are now accepted. And don't forget that these settings will affect the GNU C compiler as well! I'd expect gcc to break if these settings are in place.
One last word about LIBRARY_PATH: I'd use -L if I am planning to use a hacked version of the library, as it seems the case in your settings.
Klaus
Klaus Espenlaub wrote:
Reading the docs and doing a "strings gpc" it turns out that the env variable name is wrong: it's still GCC_EXEC_PREFIX.
Indeed. (But you don't need `strings' if you look into the source of GPC.;-)
Maybe this should be fixed or documented.
I am not sure what to do here. Integration of GPC into EGCS (--> gcc-3.0) is still planned, so it might be possible to compile Pascal files with `gcc', one day. However I can imagine that we will keep a separate `gpc' program, so it might be reasonable to search for `GPC_EXEC_PREFIX' _and_ `GCC_EXEC_PREFIX'.
Peter
-
Klaus Espenlaub -
Peter Gerwinski