On Wed, May 24, 2006 at 05:17:56PM +0000, mike wrote:
> hi folk,
>
> i worte 2 days ago but the mailserver bouncted me to the
> moderator. the mailbody was to big (build-logfiles)...
>
> my last buid looks like:.
>
> all bookscripts are used by copy&paste
> all patches are new downloaded
> the enviroment:
>
> amd opteron 2x1500MhZ
>
> [EMAIL PROTECTED] -a
> Linux Kanotix 2.6.14-kanotix64-9 #1 SMP PREEMPT Wed Dec 2005 x86_64
> GNU/Linux
>
> $PATH=/cross-tools/bin:/bin:/usr/bin
> $LFS_HOST=x86_64-cross-linux-gnu
> $LFS_TARGET=x86_64-unknown-linux-gnu
> #(by the way: can i simply change "unknown" in "somthing"?)
Probably not!
> $LFS_TARGET32=i686-pc-linux-gnu
>
> [EMAIL PROTECTED] readelf -l /bin/bash | grep Re
> [Requesting program interpreter: /lib64/ld-linux-x86-64.so.
>
> the "last" config.log that i found was:
> sources/gcc-build/x86_64-unknown-linux-gnu/32/libstdc++-v3/config.log
> but i can't found somthing like a broken library or so. (see attachment)
>
> any ideas?
From the attachment
configure:77323: checking for ld that supports -Wl,-z,relro
configure:77330: result: yes
configure:77344: checking for main in -lm
configure:77352: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
Not as explicit as I'd hoped for, the lines in
libstdc++-v3/configure are
echo "$as_me:$LINENO: checking for main in -lm" >&5
echo $ECHO_N "checking for main in -lm... $ECHO_C" >&6
if test "${ac_cv_lib_m_main+set}" = set; then
echo $ECHO_N "(cached) $ECHO_C" >&6
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lm $LIBS"
if test x$gcc_no_link = xyes; then
{ { echo "$as_me:$LINENO: error: Link tests are not allowed after
GCC_NO_EXECUTABLES." >&5
echo "$as_me: error: Link tests are not allowed after GCC_NO_EXECUTABLES." >&2;}
{ (exit 1); exit 1; }; }
fi
So, at this point it has already set gcc_no_link to yes, and now it
doesn't like that.
The setting happens at line 2413 of that configure script:
# FIXME: Cleanup?
if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
(eval $ac_link) 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }; then
gcc_no_link=no
else
gcc_no_link=yes
fi
if test x$gcc_no_link = xyes; then
# Setting cross_compile will disable run tests; it will
# also disable AC_CHECK_FILE but that's generally
# correct if we can't link.
cross_compiling=yes
EXEEXT=
else
which all sounds correct because we ARE cross-compiling here.
I can't see anything obvious here, my guess is that the error
happened in a previous package. I see Jim has asked you about the
two varieties of libm. I think we're both guessing that one of
your libc builds is broken.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
_______________________________________________
Clfs-support mailing list
[email protected]
http://ninja.linux-phreak.biz/mailman/listinfo/clfs-support
