On 20 Oct 2006 at 15:14, Waldek Hebisch wrote:
Andreas Wirooks wrote:
I found no other MinGW setupinformation than putting C:\MinGW\bin to the path. I already know that with the --automake --autobuild options because without these i got the "module/unit interface `GPC' could not be imported" error. But with one of these options i get the error listed in the subject line. Here is the output for "gpc -v --autobuild statfsdemo.pas -o statfsdemo.exe" wich is a demo program from the doc\gpc\demos directory:
C:\MinGW\doc\gpc\demos>gpc -v --autobuild statfsdemo.pas -o statfsdemo.exe Reading specs from C:/MINGW/BIN/../lib/gcc/mingw32/3.4.4/specs Configured with: ../configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=pascal --disable-win32-registry --disable-shared --enable-sjlj-exceptions --without-x --enable-interpreter --enable-hash-synchronization Thread model: win32 gpc version 20051116, based on gcc-3.4.4 (mingw special) C:/MINGW/BIN/../libexec/gcc/mingw32/3.4.4/gpc1.exe -quiet -v -iprefix C:\MINGW\BIN../lib/gcc/mingw32/3.4.4/ statfsdemo.pas -quiet -dumpbase statfsdemo.pas -auxbase statfsdemo -famtmpfile=C:\WINDOWS\TEMP/ccbxkigb.gpa -fautobuild -version -o C:\WINDOWS\TEMP/ccWldggb.s GNU Pascal version 20051116, based on gcc-3.4.4 (mingw special) (mingw32) compiled by GNU C version 3.4.4 (mingw special). GGC heuristics: --param ggc-min-expand=47 --param ggc-min-heapsize=32543 GNU Pascal Compiler PreProcessor version 20051116, based on gcc-3.4.4 (mingw special)
statfsdemo.pas:30: error: module/unit `gpc' could not be compiled
I've searched and experienced for ours. I remember, when i tried to learn c years ago (i tried to learn pascal with turbo pascal 6.0 12 years ago), that for emx (yes, the os/2 box is still lying around here) i had to setup many environment variables for the include and library pathes so that i was able to run it. I now compiled gpc.pas by hand and copied all files (.o, .gpi etc.) in the demos directory and it worked doing the commandline above. Can some hacker point me to the solution? I don't think that i have an broken installation. Befor this constellation i used different mingw's with nearly all gpc incarnations from gnu-pascal and mingw but this with this one i came at least to an exe file.
There is a problem with your installation: gpc is supposed to know where to find gpc.pas.
Absolutely.
Could you try:
gpc -print-file-name=units
"gpc -v": Reading specs from f:/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with: ../configure --enable-checking --enable-languages=pascal --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --disable-win32-registry --disable-shared --enable-sjlj-exceptions --enable-libgcj --disable-java-awt --without-x --enable-java-gc=boehm --disable-libgcj-debug --enable-interpreter --enable-hash-synchronization Thread model: win32 gpc version 20060215, based on gcc-3.4.5 (mingw special)
"gpc -print-file-name=units": f:/mingw/bin/../lib/gcc/mingw32/3.4.5/units
Both exactly the same from the "cmd" prompt and from the Msys bash prompt.
Using the prefix "/mingw" has never been a problem, and it is what GCC uses as well.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/