Next showstopper for new user; setjmp.S in glibc-2.3.6

Wed Aug 8 23:42:00 GMT 2007

I believe that adding the following compilation flag will solve that 
problem:
    -U__i686

This is because as Dan Kegel indicated in 
http://www.cygwin.com/ml/crossgcc/2004-10/msg00170.html the preprocessor 
replaces the defined symbol __i686 with its value (ie 1)

-- Emmanuel Saint-Loubert

----- Original Message ----- 
From: "Soren A" <wetware.interrupt@yahoo.com>
To: <crossgcc@sourceware.org>
Sent: Tuesday, April 10, 2007 7:52 AM
Subject: Next showstopper for new user; setjmp.S in glibc-2.3.6


> The build I am attempting using crosstool now blows up here:
>
> make  -C setjmp subdir_lib
> make[2]: Entering directory
> `/tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/glibc-2.3.6/setjmp'
> .././scripts/mkinstalldirs
> /tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc/setjmp
> mkdir
> /tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc/setjmp
> i686-unknown-linux-gnu-gcc  ../sysdeps/i386/elf/setjmp.S -c
> -I../include -I.
> -I/tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc/setjmp
> -I.. -I../libio
> -I/tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc
> -I../sysdeps/i386/elf
> -I../linuxthreads/sysdeps/unix/sysv/linux/i386
> -I../linuxthreads/sysdeps/unix/sysv/linux
> -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread
> -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
> -I../linuxthreads/sysdeps/i386/i686 -I../linuxthreads/sysdeps/i386
> -I../sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux
> -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman
> -I../sysdeps/unix/inet -I../sysdeps/unix/sysv/i386
> -I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../sysdeps/unix
> -I../sysdeps/posix -I../sysdeps/i386/i686/fpu
> -I../sysdeps/i386/i686 -I../sysdeps/i386/i486 -I../sysdeps/i386/fpu
> -I../sysdeps/i386 -I../sysdeps/wordsize-32
> -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64
> -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754
> -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem
> /tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/gcc-core-prefix/lib/gcc/i686-unknown-linux-gnu/3.4.5/include
> -isystem
> /opt/xc/gcc-3.4.5-glibc-2.3.6/i686-unknown-linux-gnu/i686-unknown-linux-gnu/include
> -D_LIBC_REENTRANT -include ../include/libc-symbols.h
> -DASSEMBLER  -DGAS_SYNTAX  -Wa,--noexecstack  -o
> /tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc/setjmp/setjmp.o
> -MD -MP -MF
> /tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc/setjmp/setjmp.o.dt
> -MT
> /tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc/setjmp/setjmp.o
> ../sysdeps/i386/elf/setjmp.S: Assembler messages:
> ../sysdeps/i386/elf/setjmp.S:63: Error: junk at end of line, first
> unrecognized character is `1'
> ../sysdeps/i386/elf/setjmp.S:64: Error: junk at end of line, first
> unrecognized character is `1'
> ../sysdeps/i386/elf/setjmp.S:65: Error: junk at end of line, first
> unrecognized character is `1'
> ../sysdeps/i386/elf/setjmp.S:66: Error: unrecognized symbol type ""
> ../sysdeps/i386/elf/setjmp.S:66: Error: junk at end of line, first
> unrecognized character is `1'
> ../sysdeps/i386/elf/setjmp.S:67: Error: junk at end of line, first
> unrecognized character is `1'
> ../sysdeps/i386/elf/setjmp.S:70: Error: expected comma after name
> `' in .size directive
> make[2]: ***
> [/tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/build-glibc/setjmp/setjmp.o]
> Error 1
> make[2]: Leaving directory
> `/tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/glibc-2.3.6/setjmp'
> make[1]: *** [setjmp/subdir_lib] Error 2
> make[1]: Leaving directory
> `/tmp/crosstool-0.43/build/i686-unknown-linux-gnu/gcc-3.4.5-glibc-2.3.6/glibc-2.3.6'
> make: *** [lib] Error 2
> ============================
>
> I figured out that my earlier message was wrong: my naughty distro
> had slipped 'dash' in while I was not looking, and the half-patched
> glibc-2.3.6 distro croaked on it. But now this is very fatal
> looking. dash has been dashed and replaced by bash, yet still the
> vetted combo of glibc-2.3.6 and gcc-3.4.5 attempted using the
> demo-i686.sh script is breaking badly. This is quite enough to
> cause insanity.
>
> (For reference to the dash issue, see
> http://sourceware.org/ml/libc-alpha/2004-01/msg00023.html and the
> link mentioned by Dan therein).
>
>
>
>
>
> ____________________________________________________________________________________
> TV dinner still cooling?
> Check out "Tonight's Picks" on Yahoo! TV.
> http://tv.yahoo.com/
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
> 


--
For unsubscribe information see http://sourceware.org/lists.html#faq