From: rolf liu <rolfliu@gmail.com>
To: linux-mips@linux-mips.org
Subject: glibc 2.3.5 cross building error
Date: Fri, 8 Jul 2005 15:20:13 -0700 [thread overview]
Message-ID: <2db32b7205070815202bc409f0@mail.gmail.com> (raw)
I am trying to cross-compile glibc 2.3.5 with linuxthread. And got the
following errors.
It seems the linker is complaining it can't find the definition of
"__fork_block". But it is really defined in "fork.c", which is at the
same directory as register-atfork.c.
Thanks
******************
mipsel-unknown-linux-gnu-gcc -mabi=32 -shared -static-libgcc -Wl,-O1
-Wl,-z,defs -Wl,-dynamic-linker=/home/rolf/toolchain/lib/ld.so.1
-B/home/rolf/toolchain/glibc-build/csu/
-Wl,--version-script=/home/rolf/toolchain/glibc-build/libc.map
-Wl,-soname=libc.so.6 -nostdlib -nostartfiles -e __libc_main
-L/home/rolf/toolchain/glibc-build
-L/home/rolf/toolchain/glibc-build/math
-L/home/rolf/toolchain/glibc-build/elf
-L/home/rolf/toolchain/glibc-build/dlfcn
-L/home/rolf/toolchain/glibc-build/nss
-L/home/rolf/toolchain/glibc-build/nis
-L/home/rolf/toolchain/glibc-build/rt
-L/home/rolf/toolchain/glibc-build/resolv
-L/home/rolf/toolchain/glibc-build/crypt
-L/home/rolf/toolchain/glibc-build/linuxthreads
-Wl,-rpath-link=/home/rolf/toolchain/glibc-build:/home/rolf/toolchain/glibc-build/math:/home/rolf/toolchain/glibc-build/elf:/home/rolf/toolchain/glibc-build/dlfcn:/home/rolf/toolchain/glibc-build/nss:/home/rolf/toolchain/glibc-build/nis:/home/rolf/toolchain/glibc-build/rt:/home/rolf/toolchain/glibc-build/resolv:/home/rolf/toolchain/glibc-build/crypt:/home/rolf/toolchain/glibc-build/linuxthreads
-o /home/rolf/toolchain/glibc-build/libc.so -T
/home/rolf/toolchain/glibc-build/shlib.lds
/home/rolf/toolchain/glibc-build/csu/abi-note.o
/home/rolf/toolchain/glibc-build/elf/soinit.os
/home/rolf/toolchain/glibc-build/libc_pic.os
/home/rolf/toolchain/glibc-build/elf/sofini.os
/home/rolf/toolchain/glibc-build/elf/interp.os
/home/rolf/toolchain/glibc-build/elf/ld.so -lgcc
/home/rolf/toolchain/glibc-build/libc_pic.os: In function `list_add_tail':
../linuxthreads/sysdeps/pthread/list.h:59: undefined reference to `__fork_block'
../linuxthreads/sysdeps/pthread/list.h:59: undefined reference to `__fork_block'
../linuxthreads/sysdeps/pthread/list.h:59: undefined reference to `__fork_block'
/home/rolf/toolchain/glibc-build/libc_pic.os: In function
`*__GI___register_atfork':
../linuxthreads/sysdeps/unix/sysv/linux/register-atfork.c:84:
undefined reference to `__fork_block'
../linuxthreads/sysdeps/unix/sysv/linux/register-atfork.c:73:
undefined reference to `__fork_block'
/home/rolf/toolchain/glibc-build/libc_pic.os:../linuxthreads/sysdeps/unix/sysv/linux/unregister-atfork.c:35:
more undefined references to `__fork_block' follow
collect2: ld returned 1 exit status
make[1]: *** [/home/rolf/toolchain/glibc-build/libc.so] Error 1
make[1]: Leaving directory `/home/rolf/toolchain/glibc-2.3.5'
make: *** [all] Error 2
reply other threads:[~2005-07-08 22:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2db32b7205070815202bc409f0@mail.gmail.com \
--to=rolfliu@gmail.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox