Re: possible error for cross-gcc-2.3.5-glibc-2.3.2?

[Carlos de <carlos_desa at yahoo dot com>]

hi
   I'm building all this on a P4 running Suse 9.1 pro
and yes it has the libunwind library in /usr/lib.
grepped thru the crostool build dir and found lunwind
mentioned in the config.log for the core-gcc build
among others--
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc-core/gcc/config.log:configure:4953:
checking for main in -lunwind
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc-core/gcc/config.log:configure:4968:
gcc -o conftest -g -O2   conftest.c -lunwind   1>&5
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc-core/gcc/auto-host.h:/*
Define if gcc should use -lunwind. */
Binary file
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/g++
matches
Binary file
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/cpp
matches
Binary file
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/xgcc
matches
Binary file
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/gcc.o
matches
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/specs:%{msoft-float:-lfloat}
%{static|static-libgcc:-lgcc -lgcc_eh
-lunwind}%{!static:%{!static-libgcc:%{!shared-libgcc:-lgcc
--as-needed -lgcc_s%M
--no-as-needed}%{shared-libgcc:-lgcc_s%M%{!shared:
-lgcc}}}}
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/config.log:configure:4953:
checking for main in -lunwind
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/config.log:configure:4968:
gcc -o conftest -g -O2   conftest.c -lunwind   1>&5
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/auto-host.h:/*
Define if gcc should use -lunwind. */
Binary file
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/g++spec.o
matches
Binary file
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/g++-cross
matches
Binary file
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/gcc/gcc-cross
matches
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/arm-9tdmi-linux-gnu/libstdc++-v3/config.log:/home/carlos/crossgcc2.95.3_ARM_2.6/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/arm-9tdmi-linux-gnu/bin/ld:
cannot find -lunwind
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/build-gcc/arm-9tdmi-linux-gnu/libstdc++-v3/config.log:/home/carlos/crossgcc2.95.3_ARM_2.6/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/arm-9tdmi-linux-gnu/bin/ld:
cannot find -lunwind
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/cp/g++spec.c:#
 define LIBUNWIND "-lunwind"
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/gcc.c:
		    " -lunwind"
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/config.in:/*
Define if gcc should use -lunwind. */
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/configure:echo
$ac_n "checking for main in -lunwind""... $ac_c" 1>&6
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/configure:echo
"configure:4953: checking for main in -lunwind" >&5
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/configure:LIBS="-lunwind
 $LIBS"
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/configure.in:
[Define if gcc should use -lunwind.])
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/config/t-libunwind:#
Override the default value from t-slibgcc-elf-ver and
mention -lunwind
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/config/t-libunwind:SHLIB_LC
= -lunwind -lc
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/ChangeLog:
      * gcc.c (init_spec): Pass -lunwind to
init_gcc_specs in eh_name
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/gcc/ChangeLog:
* gcc.c (init_spec) [USE_LIBUNWIND_EXCEPTIONS]:
Mention -lunwind
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/libstdc++-v3/aclocal.m4:
   LIBUNWIND_FLAG="-lunwind"
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/libstdc++-v3/configure:
   LIBUNWIND_FLAG="-lunwind"
build/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2/gcc-3.3.5/libstdc++-v3/acinclude.m4:
   LIBUNWIND_FLAG="-lunwind"
buildlogs/0.28/powerpc-440-gcc-3.3.4-glibc-2.3.3.txt:checking
for main in -lunwind... no
buildlogs/0.28/arm-iwmmxt-gcc-3.3.4-glibc-2.3.3.txt:checking
for main in -lunwind... no
patches/glibc-20040822/glibc-2.3.3-libeh-kludge.patch:
 gnulib := -lgcc $(libgcc_eh) -lunwind
patches/glibc-20040822/glibc-2.3.3-libeh-kludge.patch:
 static-gnulib := -lgcc -lgcc_eh -lunwind
patches/glibc-20040827/glibc-2.3.3-libeh-kludge.patch:
 gnulib := -lgcc $(libgcc_eh) -lunwind
patches/glibc-20040827/glibc-2.3.3-libeh-kludge.patch:
 static-gnulib := -lgcc -lgcc_eh -lunwind

    From what i can read from above it only seems to
be added as an  option for a different version of
glibc.

    anything i can do to prevent the above happening?

thanks

Carlos
 --- Ryan.Oliver@pha.com.au wrote: 
> 
> 
> 
> 
> 
> > /home/carlos/crossgcc2.95.3
> _ARM_2.6/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2
> /bin/arm-9tdmi-linux-gnu-gcc
> -static hello.c -o arm-9tdmi-linux-gnu-hello-static
> > /home/carlos/crossgcc2.95.3
> _ARM_2.6/arm-9tdmi-linux-gnu/gcc-3.3.5-glibc-2.3.2
> /lib/gcc-lib/arm-9tdmi-linux-gnu/3.3.5
> /../../../../arm-9tdmi-linux-gnu/bin/ld: cannot find
> -lunwind
> > collect2: ld returned 1 exit status
> 
> Interesting, somehow gcc has determined during
> configure that you have
> libunwind (if this happens it sets itself up to use
> the unwind routines
> from there instead of libgcc_s, and automatically
> adds -lunwind to its
> link).
> 
> Quite possibly gcc configure goofed and tested for
> -lunwind against
> against the build-host.
> 
> You aren't by chance building on ia64, or does your
> build-host have
> libunwind?
> 
>  Regards
> Ryan
> 
>  


	
	
		
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun!  http://uk.messenger.yahoo.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com