Hi folks,
I'm trying to build the gpc-20030830 alpha version on my MinGW system. In my current attempt I'm directly compiling from within the gcc-3.2.1 core directory. I start building with the command
./configure --prefix=C:/MinGW --enable-languages=pascal
Then `make' always aborts with the following message:
make[2]: Entering directory `/mysoftware/gcc-3.2.1/gcc/p/rts' make[2]: Nothing to be done for `generated-files'. make[2]: Leaving directory `/mysoftware/gcc-3.2.1/gcc/p/rts' cd ./p/rts && make -f Makefile.in srcdir=. GCC_VERSION="3.2.1" SHELL="/bin/sh" CFLAGS="-g -O2" PFLAGS="" AR="ar" AR_FLAGS="rc" RANLIB="ranlib" RANLIB_TEST="[ -f ranlib ] || ( [ "i686-pc-mingw32" = "i686-pc-mingw32" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" RTSFLAGS="" DESTDIR="../.." generated-files make[2]: Entering directory `/mysoftware/gcc-3.2.1/gcc/p/rts' make[2]: Nothing to be done for `generated-files'. make[2]: Leaving directory `/mysoftware/gcc-3.2.1/gcc/p/rts' cd ./p/rts && make CC="`echo /mysoftware/gcc-3.2.1/gcc/xgcc -B/mysoftware/gcc-3.2.1/gcc/ -BC:/MinGW/i686-pc-mingw32/bin/ -BC:/MinGW/i686-pc-mingw32/lib/ -isystem C:/MinGW/i686-pc-mingw32/include' ' | sed -e 's,(-[BI])([^/][^:]),\1../../\2,g;s,^([^/][^:]*/),../../\1,'`" PC="`echo ./xgpc -B./' ' | sed -e 's,(-[BI])([^/][^:]),\1../../\2,g;s,^([^/][^:]*/),../../\1,'`" GCC_VERSION="3.2.1" SHELL="/bin/sh" CFLAGS="-g -O2" PFLAGS="" AR="ar" AR_FLAGS="rc" RANLIB="ranlib" RANLIB_TEST="[ -f ranlib ] || ( [ "i686-pc-mingw32" = "i686-pc-mingw32" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" RTSFLAGS="" DESTDIR="../.." all make[2]: Entering directory `/mysoftware/gcc-3.2.1/gcc/p/rts' ../.././xgpc -B../.././ -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -g -O2 --unit-path=/mysoftware/gcc-3.2.1/gcc/p/rts --automake --print-needed-options "endian.pas" 2> "needed-options" || true if grep -v '^--' "needed-options" > /dev/null; then echo "needed-options: `cat "needed-options"`" >&2; rm -f "needed-options"; false; else true; fi make[2]: Leaving directory `/mysoftware/gcc-3.2.1/gcc/p/rts' make[1]: Leaving directory `/mysoftware/gcc-3.2.1/gcc' make[1]: Circular libgcc.a <- pascal dependency dropped. needed-options: 0 [main] sh 2240 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump make[2]: *** [needed-options] Error 1 make[1]: *** [pascal.rts] Error 2 make: *** [all-gcc] Error 2
The file "needed-options" doesn't exist at all. If I `touch' it, `make' aborts with
make[2]: Entering directory `/mysoftware/gcc-3.2.1/gcc/p/rts' make[2]: Nothing to be done for `generated-files'. make[2]: Leaving directory `/mysoftware/gcc-3.2.1/gcc/p/rts' cd ./p/rts && make -f Makefile.in srcdir=. GCC_VERSION="3.2.1" SHELL="/bin/sh" CFLAGS="-g -O2" PFLAGS="" AR="ar" AR_FLAGS="rc" RANLIB="ranlib" RANLIB_TEST="[ -f ranlib ] || ( [ "i686-pc-mingw32" = "i686-pc-mingw32" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" RTSFLAGS="" DESTDIR="../.." generated-files make[2]: Entering directory `/mysoftware/gcc-3.2.1/gcc/p/rts' make[2]: Nothing to be done for `generated-files'. make[2]: Leaving directory `/mysoftware/gcc-3.2.1/gcc/p/rts' cd ./p/rts && make CC="`echo /mysoftware/gcc-3.2.1/gcc/xgcc -B/mysoftware/gcc-3.2.1/gcc/ -BC:/MinGW/i686-pc-mingw32/bin/ -BC:/MinGW/i686-pc-mingw32/lib/ -isystem C:/MinGW/i686-pc-mingw32/include' ' | sed -e 's,(-[BI])([^/][^:]),\1../../\2,g;s,^([^/][^:]*/),../../\1,'`" PC="`echo ./xgpc -B./' ' | sed -e 's,(-[BI])([^/][^:]),\1../../\2,g;s,^([^/][^:]*/),../../\1,'`" GCC_VERSION="3.2.1" SHELL="/bin/sh" CFLAGS="-g -O2" PFLAGS="" AR="ar" AR_FLAGS="rc" RANLIB="ranlib" RANLIB_TEST="[ -f ranlib ] || ( [ "i686-pc-mingw32" = "i686-pc-mingw32" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" RTSFLAGS="" DESTDIR="../.." all make[2]: Entering directory `/mysoftware/gcc-3.2.1/gcc/p/rts' /mysoftware/gcc-3.2.1/gcc/xgcc -B/mysoftware/gcc-3.2.1/gcc/ -BC:/MinGW/i686-pc-mingw32/bin/ -BC:/MinGW/i686-pc-mingw32/lib/ -isystem C:/MinGW/i686-pc-mingw32/include -c -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -g -O2 rts.c make[2]: Leaving directory `/mysoftware/gcc-3.2.1/gcc/p/rts' make[1]: Leaving directory `/mysoftware/gcc-3.2.1/gcc' make[1]: Circular libgcc.a <- pascal dependency dropped. 0 [main] sh 1268 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump make[2]: *** [rts.o] Segmentation fault (core dumped) make[1]: *** [pascal.rts] Error 2 make: *** [all-gcc] Error 2
Any idea what I'm doing wrong here?
Thanks,
Markus
On 10 Jan 2004 at 12:32, Markus Gerwinski wrote:
Hi folks,
I'm trying to build the gpc-20030830 alpha version on my MinGW system. In my current attempt I'm directly compiling from within the gcc-3.2.1 core directory. I start building with the command
./configure --prefix=C:/MinGW --enable-languages=pascal
Then `make' always aborts with the following message:
[...]
What environment are you using to build? Perhaps the "c:/mingw" prefix is a problem. Attached is an amended version of the script that I use (I build under the Mingw + MSYS environment). The script is based on the output of "gcc -v" which shows the configure parameters that were used to build gcc.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~african_chief/
The following section of this message contains a file attachment prepared for transmission using the Internet MIME message format. If you are using Pegasus Mail, or any other MIME-compliant system, you should be able to save it or view it from within your mailer. If you cannot, please ask your system administrator for assistance.
---- File information ----------- File: gpc-3.3.1-build.sh Date: 10 Jan 2004, 13:20 Size: 360 bytes. Type: Unknown
Prof A Olowofoyeku (The African Chief) wrote:
What environment are you using to build? Perhaps the "c:/mingw" prefix is a problem.
I'm using msys. Usually it deals well with "c:/".
Attached is an amended version of the script that I use (I build under the Mingw + MSYS environment). The script is based on the output of "gcc -v" which shows the configure parameters that were used to build gcc.
Thanks! Could you give me some instructions on how to use the script? Where in my directory tree should I put it? Should I unpack the gpc and gcc tarballs in a certain manner before? (E.g. unpack gpc right into the gcc-3.2.1 dir tree or something?)
My first attempts were fruitless: Putting the script into the gcc subdirectory of gcc-3.2.1 (seemed logical to me, since you're calling ../configure in the script) yielded the error message:
make: *** No rule to make target `../libiberty/libiberty.a', needed by `gengenrtl.exe'. Stop.
Changing the "../configure" into "./configure" and putting the script into gcc-3.2.1/ first seemed to run well first, but it aborted after a while complaining about undefined references to the libgpc. Changing the --prefix clause from "/mingw" into "/c/mingw" doesn't change things here. After I `made clean' and repeated with these adjustments, the system headers (e.g. time.h) weren't found anymore.
What now?
Thank you,
Markus
On 10 Jan 2004 at 20:14, Markus Gerwinski wrote:
Prof A Olowofoyeku (The African Chief) wrote:
What environment are you using to build? Perhaps the "c:/mingw" prefix is a problem.
I'm using msys. Usually it deals well with "c:/".
Attached is an amended version of the script that I use (I build under the Mingw + MSYS environment). The script is based on the output of "gcc -v" which shows the configure parameters that were used to build gcc.
Thanks! Could you give me some instructions on how to use the script? Where in my directory tree should I put it? Should I unpack the gpc and gcc tarballs in a certain manner before? (E.g. unpack gpc right into the gcc-3.2.1 dir tree or something?)
[...]
You can put the script anywhere in the "PATH". Mine is in the /mingw/bin directory. The procedure that I use is this: 1. untar the gcc sources 2. cd gcc-3.3.1/gcc/ 3. tar -zxvf /tmp/gpc-20030830.tar.gz 4. cd gpc-20030830/ && mv p .. && cd .. && rmdir gpc-20030830/ 5. cd .. 6. mkdir build/ 7. cd build/ 8. /mingw/bin/gpc-3.3.1-build.sh
If your Mingw and MSYS are correctly configured, this will work. And you can of course make a script out of these steps.
BTW: I never use the pristine gnu sources for gcc. I prefer to use the relevant "mingw special" version of the gcc sources, which are on the Mingw web site.
Finally, I use Windows 2000 or XP. I have no idea whether attempting to build under Windows 9x/Me will be problematic or not. Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.bigfoot.com/~african_chief/
On 10 Jan 2004 at 12:32, Markus Gerwinski wrote:
0 [main] sh 1268 open_stackdumpfile: Dumping stack trace to sh.exe.stackdumpmake[2]: *** [rts.o] Segmentation fault (core dumped)
Are you running MSYS-1.0.10-rc-2? Version 1.0.10rc1 and prior are known to produce stackfaults in "sh" while building. See:
http://sourceforge.net/mailarchive/message.php?msg_id=5958706
for example. See also the last paragraph of:
http://sourceforge.net/mailarchive/message.php?msg_id=5968244
Also, version 1.0.10rc3 has a problem with "rxvt" creating console windows for each invocation of gcc during a build. I have been able to consistently build GPC successfully only with 1.0.10rc2.
-- Dave
-
J. David Bryan -
Markus Gerwinski -
Prof A Olowofoyeku (The African Chief)