From: Anh V. <An...@ud...> - 2005-04-18 17:15:49
|
<< >>> aar...@aa... 04/18/05 5:55 AM >>> Rolf Ebert wrote: > I am having difficulties bootstrapping gcc 4.0 Ada on mingw/msys. > Program received signal SIGSEGV, Segmentation fault. > 0x004034b7 in __gnat_install_SEH_handler (ER=3D0x77c0b814) The patch for this is here: <http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01459.html>. This is fixed on mainline, but apparently not on branch. I guess its too late to fix this for 4.0.0, but maybe for 4.0.1. I've been starved for both real time, and computer cycles, lately. >> On the same subject, I got different kind of errors, as shown below, = except that I built for Win2K. I am a newby when it comes to building = compiler such as gcc. Based on this error message, xgcc did not seem to = know where to reference C standard libraries.=20 ...cut off... ./xgcc -B./ -B/usr/local/i686-pc-mingw32/bin/ -isystem /usr/local/i686-pc-m= ingw3 2/include -isystem /usr/local/i686-pc-mingw32/sys-include -L/c/build4= /gcc/../ld -O2 -I../../gcc-4.0.0-20050410/gcc/../winsup/w32api/include = -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototy= pes -Wold-style-definition -isystem ./include -g -DHAVE_GTHR_DEFAULT = -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEE DED -I. -I. -I../../gcc-4.0.0-20050410/= gcc -I../../gcc-4.0.0-20050410/gcc/. -I. ./../gcc-4.0.0-20050410/gcc/../inc= lude -I./../intl -I../../gcc-4.0.0-20050410/gc c/../libcpp/include = -DL_muldi3 -c ../../gcc-4.0.0-20050410/gcc/libgcc2.c -o lib gcc/./_muldi3.o= In file included from ../../gcc-4.0.0-20050410/gcc/libgcc2.c:41: ../../gcc-4.0.0-20050410/gcc/tsystem.h:90:19: error: stdio.h: No such file = or di rectory ../../gcc-4.0.0-20050410/gcc/tsystem.h:93:23: error: sys/types.h: No such = file o r directory ../../gcc-4.0.0-20050410/gcc/tsystem.h:96:19: error: errno.h: No such file = or di rectory ../../gcc-4.0.0-20050410/gcc/tsystem.h:103:20: error: string.h: No such = file or directory ../../gcc-4.0.0-20050410/gcc/tsystem.h:104:20: error: stdlib.h: No such = file or directory ../../gcc-4.0.0-20050410/gcc/tsystem.h:105:20: error: unistd.h: No such = file or directory In file included from ./include/limits.h:122, from ./include/syslimits.h:7, from ./include/limits.h:11, from ../../gcc-4.0.0-20050410/gcc/tsystem.h:108, from ../../gcc-4.0.0-20050410/gcc/libgcc2.c:41: ./include/limits.h:122:61: error: no include path in which to search for = limits. h In file included from ../../gcc-4.0.0-20050410/gcc/libgcc2.c:41: ../../gcc-4.0.0-20050410/gcc/tsystem.h:111:18: error: time.h: No such file = or di rectory In file included from ./tm.h:9, from ../../gcc-4.0.0-20050410/gcc/libgcc2.c:43: ../../gcc-4.0.0-20050410/gcc/config/i386/cygming.h:349: error: parse error = befor e '*' token ../../gcc-4.0.0-20050410/gcc/config/i386/cygming.h:349: warning: function = declar ation isn't a prototype make[3]: *** [libgcc/./_muldi3.o] Error 1 make[3]: Leaving directory `/c/build4/gcc' make[2]: *** [libgcc.a] Error 2 make[2]: Leaving directory `/c/build4/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/c/build4/gcc' make: *** [bootstrap] Error 2 =20 |
From: Anh V. <An...@ud...> - 2005-04-21 20:34:44
|
Aaron, Thank you very much for your help. I will do it right the way. In = addition, I will try to work on gcc-4.0.0 since it is just released today. = I hope it turns out OK. If not, I will post next trouble I have. AV >>> aar...@aa... 04/20/05 3:52 PM >>> Anh Vo wrote: > Based on this error message, xgcc did not seem to know where to = reference C standard libraries.=20 The easy way to fix this is to install mingwrt and w32api into the same prefix GCC is installed into, before building. |
From: Anh V. <An...@ud...> - 2005-04-25 20:53:19
|
The error message below shows the problem I encountered in the stage1 of = the bootstrap process. As indicated, the failure occurs during binding of = gnat1drv. In addition, this failure also triggers an application error = windows (named gnatbind.exe - Application Error on Windows 2K, hit = Terminate button to exit and hit Cancel but to debug) containing the = following text. The instruction at "0x004034b7" referenced memory at "0xffffffff". The memory could not be read. On Windows XP Home Edition, a different kind of error window (with two = buttons one for Send Report and the other for Not Send Report). This failures presents a showstopper for me. I will be appreciated if any = one can provides any suggestion for fixing it. Again, thank you in advance = for your help. ... cut off ... stage1/xgcc.exe -Bstage1/ -B/usr/local/i686-pc-mingw32/bin/ -c -g -O2 = -gnatpg -gnata -I- -I. -Iada -I../../gcc-4.0.0/gcc/ada ../../gcc-4.0.0/gcc/= ada/back_end.adb -o ada/back_end.o stage1/xgcc.exe -Bstage1/ -B/usr/local/i686-pc-mingw32/bin/ -c -g -O2 = -gnatpg -gnata -I- -I. -Iada -I../../gcc-4.0.0/gcc/ada ../../gcc-4.0.0/gcc/= ada/gnat1drv.adb -o ada/gnat1drv.o stage1/gnatbind -C -I- -I. -Iada -I../../gcc-4.0.0/gcc/ada -o ada/b_gnat1.c= -n ada/gnat1drv.ali make[2]: *** [ada/b_gnat1.c] Error 5 make[2]: Leaving directory `/g/build-4.0.0/gcc' make[1]: *** [stage2_build] Error 2 make[1]: Leaving directory `/g/build-4.0.0/gcc' make: *** [bootstrap] Error 2 Aaron, Thank you very much for your help. I will do it right the way. In = addition, I will try to work on gcc-4.0.0 since it is just released today. = I hope it turns out OK. If not, I will post next trouble I have. AV >>> aar...@aa... 04/20/05 3:52 PM >>> Anh Vo wrote: > Based on this error message, xgcc did not seem to know where to = reference C standard libraries.=20 The easy way to fix this is to install mingwrt and w32api into the same prefix GCC is installed into, before building. |
From: Rolf E. <rol...@gm...> - 2005-04-26 12:19:09
|
On Mon, 25 Apr 2005 15:53:20 -0500, Anh Vo <An...@ud...> wrote: > The error message below shows the problem I encountered in the stage1 of > the bootstrap process. As indicated, the failure occurs during binding > of gnat1drv. In addition, this failure also triggers an application > error windows (named gnatbind.exe - Application Error on Windows 2K, hit > Terminate button to exit and hit Cancel but to debug) containing the > following text. I had the same problem and Aaron already replied to use the patch at http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01459.html That patch is only partly applied on the gcc-4.0.0 branch. Patch will complain as it cannot apply all hunks. I manually verified the failing parts and you can safely ignore them. See my mail from April 19 (and Aaron's messages) on this list. HTH Rolf |
From: Rolf E. <rol...@gm...> - 2006-04-01 20:04:14
|
According to gcc PR24382 I provide the absolute path to ld when running configure. ../gcc-4.1.0/configure --enable-languages=c,c++,ada --disable-nls --disable-fixincludes --enable-threads=win32 --host=mingw32 --build=mingw32 --target=mingw32 --with-ld=/mingw/bin/ld --with-as=/mingw/bin/as Then I had to patch gcc/Makefile.in. If not, the gcc build cannot find libiberty.a although I don't build in the source directory: around line 80 in gcc/Makefile.in # ifeq ($(host_subdir),.) build_objdir := ../$(build_subdir) # else # build_objdir := ../../$(build_subdir) # endif When building the Ada tools the make process cannot find the assembler (or is it something else?) even though I provide also an absolute path to as. make[7]: Entering directory `/d/Data/Development/gcc-cvs/build_4.1.0/gcc/ada/rts' ../../xgcc -B../../ -c -DIN_GCC `echo -g -O2 -fexceptions -DIN_RTS |sed -e 's/-pedantic//g' -e 's/-Wtraditional//g'` -I. -I.. -I../.. -I/d/Data/Development/gcc-cvs/gcc-4.1.0/gcc/ada -I/d/Data/Development/gcc-cvs/gcc-4.1.0/gcc/ada/../config -I/d/Data/Development/gcc-cvs/gcc-4.1.0/gcc/ada/../../include -I/d/Data/Development/gcc-cvs/gcc-4.1.0/gcc/ada/.. -I./../.. /d/Data/Development/gcc-cvs/gcc-4.1.0/gcc/ada/adaint.c \ -o adaint.o ..\..\as: ..\..\as: No such file or directory make[7]: *** [adaint.o] Error 1 make[7]: Leaving directory `/d/Data/Development/gcc-cvs/build_4.1.0/gcc/ada/rts' make[6]: *** [gnatlib] Error 2 make[6]: Leaving directory `/d/Data/Development/gcc-cvs/build_4.1.0/gcc/ada' make[5]: *** [gnatlib-shared-win32] Error 2 make[5]: Leaving directory `/d/Data/Development/gcc-cvs/build_4.1.0/gcc/ada' make[4]: *** [gnatlib-shared] Error 2 make[4]: Leaving directory `/d/Data/Development/gcc-cvs/build_4.1.0/gcc/ada' make[3]: *** [gnatlib-shared] Error 2 make[3]: Leaving directory `/d/Data/Development/gcc-cvs/build_4.1.0/mingw32/libada' make[2]: *** [all-target-libada] Error 2 make[2]: Leaving directory `/d/Data/Development/gcc-cvs/build_4.1.0' make[1]: *** [all] Error 2 make[1]: Leaving directory `/d/Data/Development/gcc-cvs/build_4.1.0' make: *** [bootstrap] Error 2 Has anybody seen this problem before? Any hints how to solve it? Rolf |
From: Anh V. <An...@ud...> - 2005-04-27 02:23:16
|
I see. Thanks very much for your information. I will resume the building = process after the PRs shown in the link are fixed. AV >>> rol...@gm... 04/26/05 5:18 AM >>> On Mon, 25 Apr 2005 15:53:20 -0500, Anh Vo <An...@ud...> wrote: > The error message below shows the problem I encountered in the stage1 of = =20 > the bootstrap process. As indicated, the failure occurs during binding = =20 > of gnat1drv. In addition, this failure also triggers an application =20 > error windows (named gnatbind.exe - Application Error on Windows 2K, hit = =20 > Terminate button to exit and hit Cancel but to debug) containing the =20 > following text. I had the same problem and Aaron already replied to use the patch at http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01459.html=20 That patch is only partly applied on the gcc-4.0.0 branch. Patch will =20 complain as it cannot apply all hunks. I manually verified the failing = =20 parts and you can safely ignore them. See my mail from April 19 (and =20 Aaron's messages) on this list. |
From: Anh V. <An...@ud...> - 2005-04-28 20:47:58
|
It is interesting that I built it successfully using cygwin having = gcc-3.3.3. There must be some thing difference between gcc-3.3.3 and = gcc-3.4.2. In addition, one drawback of using cygwin is that it take too = long, close to a day, to complete the build.=20 I see. Thanks very much for your information. I will resume the building = process after the PRs shown in the link are fixed. AV >>> rol...@gm... 04/26/05 5:18 AM >>> On Mon, 25 Apr 2005 15:53:20 -0500, Anh Vo <An...@ud...> wrote: > The error message below shows the problem I encountered in the stage1 of = =20 > the bootstrap process. As indicated, the failure occurs during binding = =20 > of gnat1drv. In addition, this failure also triggers an application =20 > error windows (named gnatbind.exe - Application Error on Windows 2K, hit = =20 > Terminate button to exit and hit Cancel but to debug) containing the =20 > following text. I had the same problem and Aaron already replied to use the patch at http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01459.html=20 That patch is only partly applied on the gcc-4.0.0 branch. Patch will =20 complain as it cannot apply all hunks. I manually verified the failing = =20 parts and you can safely ignore them. See my mail from April 19 (and =20 Aaron's messages) on this list. |
From: Aaron W. L. <aar...@aa...> - 2005-04-20 22:52:28
|
Anh Vo wrote: > Based on this error message, xgcc did not seem to know where to reference C standard libraries. The easy way to fix this is to install mingwrt and w32api into the same prefix GCC is installed into, before building. Aaron |