Re: [Gm2] gm2-0.4 released

[Gaius Mulley]

Izo <address@hidden> writes:

> Platform: ix86 (PIV), Linux, kernel-2.4.19, gcc-3.2, glibc-2.2.5
> 
> Got the tarballs for gcc-3.2.3 and gcc-3.3.1 from GNU mirror
> 
> 1. Build for gcc-3.2.3:
> 
> (SHLIB_LINK='/hda6/home/iztokk/c/gm2/build/gcc-host/gcc/xgcc
> -B/hda6/home/iztokk/c/gm2/build/gcc-host/gcc/
> -B/usr/local/i686-pc-linux-gnu/bin/
> -B/usr/local/i686-pc-linux-gnu/lib/ -isystem
> /usr/local/i686-pc-linux-gnu/include -O2  -DIN_GCC    -W -Wall
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
> ./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
> -D__GCC_FLOAT_NOT_NEEDED  -shared -nodefaultlibs
> -Wl,address@hidden@.so.1
> -Wl,address@hidden@ -o
> @shlib_dir@@address@hidden @multilib_flags@ @shlib_objs@ -lc &&
> rm -f @address@hidden && ln -s @shlib_dir@@address@hidden
> @address@hidden' \
> SHLIB_MULTILIB=''; \
> gcc -c -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long
> -DHAVE_CONFIG_H    -DSTANDARD_STARTFILE_PREFIX=\"../../../\"
> -DSTANDARD_EXEC_PREFIX=\"/usr/local/lib/gcc-lib/\"
> -DDEFAULT_TARGET_VERSION=\"3.2.3\"
> -DDEFAULT_TARGET_MACHINE=\"i686-pc-linux-gnu\"
> -DSTANDARD_BINDIR_PREFIX=\"/usr/local/bin/\"
> -DTOOLDIR_BASE_PREFIX=\"../../../../\" `test "X${SHLIB_LINK}" = "X" ||
> test "yes" != "yes" || echo "-DENABLE_SHARED_LIBGCC"` `test
> "X${SHLIB_MULTILIB}" = "X" || echo "-DNO_SHARED_LIBGCC_MULTILIB"` \
>         -DLIBSUBDIR=\"/usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.3\" \
>         -I. -I. -I../../../gcc-3.2.3/gcc
> -I../../../gcc-3.2.3/gcc/. -I../../../gcc-3.2.3/gcc/config
> -I../../../gcc-3.2.3/gcc/../include
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c -o gm2spec.o)
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c: In function `lang_specific_driver':
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:187: warning: passing arg 3 of
> `insert_arg' from incompatible pointer type
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:189: warning: passing arg 2 of
> `add_default_directories' from incompatible pointer type
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c: At top level:
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:203: warning: array type has
> incomplete element type
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:203: elements of array
> `lang_specific_spec_functions' have incomplete type
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:205: warning: excess elements in
> struct initializer
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:205: warning: (near
> initialization for `lang_specific_spec_functions[0]')
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:205: warning: excess elements in
> struct initializer
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:205: warning: (near
> initialization for `lang_specific_spec_functions[0]')
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:203: warning: array
> `lang_specific_spec_functions' assumed to have one element
> ../../../gcc-3.2.3/gcc/gm2/gm2spec.c:203: storage size of
> `lang_specific_spec_functions' isn't known
> make[1]: *** [gm2spec.o] Error 1
> make[1]: Leaving directory `/hda6/home/iztokk/c/gm2/build/gcc-host/gcc'
> make: *** [all-gcc] Error 2
> ./gm2-out-of-the-box: line 53: syntax error near unexpected token `fi'
> ./gm2-out-of-the-box: line 53: `fi'


Hi Iztok,

yes the build for the gcc-3.2.* will now fail. The build for 3.3.1
should succeed. Perhaps we need to keep backwards compatibility?

> 
> 2. Build for 3.3.1
> 
> ./xgcc -B./ -B/usr/local/gcc-3.3.1+gm2/i686-pc-linux-gnu/bin/ -isystem
> /usr/local/gcc-3.3.1+gm2/i686-pc-linux-gnu/include -isystem
> /usr/local/gcc-3.3.1+gm2/i686-pc-linux-gnu/sys-include -O2  -DIN_GCC
> -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
> -D__GCC_FLOAT_NOT_NEEDED  -shared -nodefaultlibs
> -Wl,--soname=libgcc_s.so.1 -Wl,--version-script=libgcc/./libgcc.map -o
> libgcc_s.so.1   libgcc/./_muldi3.o libgcc/./_negdi2.o
> libgcc/./_lshrdi3.o libgcc/./_ashldi3.o libgcc/./_ashrdi3.o
> libgcc/./_ffsdi2.o libgcc/./_clz.o libgcc/./_cmpdi2.o
> libgcc/./_ucmpdi2.o libgcc/./_floatdidf.o libgcc/./_floatdisf.o
> libgcc/./_fixunsdfsi.o libgcc/./_fixunssfsi.o libgcc/./_fixunsdfdi.o
> libgcc/./_fixdfdi.o libgcc/./_fixunssfdi.o libgcc/./_fixsfdi.o
> libgcc/./_fixxfdi.o libgcc/./_fixunsxfdi.o libgcc/./_floatdixf.o
> libgcc/./_fixunsxfsi.o libgcc/./_fixtfdi.o libgcc/./_fixunstfdi.o
> libgcc/./_floatditf.o libgcc/./_clear_cache.o libgcc/./_trampoline.o
> libgcc/./__main.o libgcc/./_exit.o libgcc/./_absvsi2.o
> libgcc/./_absvdi2.o libgcc/./_addvsi3.o libgcc/./_addvdi3.o
> libgcc/./_subvsi3.o libgcc/./_subvdi3.o libgcc/./_mulvsi3.o
> libgcc/./_mulvdi3.o libgcc/./_negvsi2.o libgcc/./_negvdi2.o
> libgcc/./_ctors.o libgcc/./_divdi3.o libgcc/./_moddi3.o
> libgcc/./_udivdi3.o libgcc/./_umoddi3.o libgcc/./_udiv_w_sdiv.o
> libgcc/./_udivmoddi4.o  libgcc/./unwind-dw2.o
> libgcc/./unwind-dw2-fde-glibc.o libgcc/./unwind-sjlj.o
> libgcc/./unwind-c.o -lc && rm -f libgcc_s.so && ln -s libgcc_s.so.1
> libgcc_s.so
> make[4]: Leaving directory
> `/hda6/home/iztokk/c/gm2/build-3.3.1/gcc-host/gcc'
> pngtopnm ../../../gcc-3.3.1/gcc/gm2/images/gnupng | pnmtops -noturn >
> ../../../gcc-3.3.1/gcc/gm2/images/gnu.eps
> /bin/sh: line 1: pngtopnm: command not found
> /bin/sh: line 1: pnmtops: command not found
> make[3]: *** [../../../gcc-3.3.1/gcc/gm2/images/gnu.eps] Error 127
> make[3]: Leaving directory
> `/hda6/home/iztokk/c/gm2/build-3.3.1/gcc-host/gcc'
> make[2]: *** [stage1_build] Error 2
> make[2]: Leaving directory
> `/hda6/home/iztokk/c/gm2/build-3.3.1/gcc-host/gcc'
> cp: cannot stat `stage2/gm2/cc1gm2': No such file or directory
> make[1]: *** [cc1gm2] Error 1
> make[1]: Leaving directory
> `/hda6/home/iztokk/c/gm2/build-3.3.1/gcc-host/gcc'
> make: *** [all-gcc] Error 2
> 
> I understand that the pngtopnm and pnmtops are not found. Butthe next
> time I do make in gcc-host directory, it comes through  - so obviously
> something is not quite correct in the build process.

ahh yes it would seem that the `./configure' is not detecting the
absence of these tools. The make break first time (leaving a zero byte
file?) and second time it falsely succeeds. I think the solution is
either to cvs checkin the gnu image we are attempting to build or
alternatively make ./configure halt on absence of pnm tools..

Gaius