From: Antoine Martin <antoine@nagafix.co.uk>
To: User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] Fedora 12 can't link with libc.a
Date: Sun, 27 Dec 2009 19:55:56 +0700 [thread overview]
Message-ID: <4B37595C.8050002@nagafix.co.uk> (raw)
Exact same error as this bug:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=10893
LD .tmp_vmlinux1
/usr/lib/gcc/x86_64-redhat-linux/4.4.2/../../../../lib64/libc.a(elf-init.o):
In function `__libc_csu_init':
(.text+0x65): undefined reference to `__rela_iplt_end'
/usr/lib/gcc/x86_64-redhat-linux/4.4.2/../../../../lib64/libc.a(elf-init.o):
In function `__libc_csu_init':
(.text+0x6e): undefined reference to `__rela_iplt_start'
/usr/lib/gcc/x86_64-redhat-linux/4.4.2/../../../../lib64/libc.a(elf-init.o):
In function `__libc_csu_init':
(.text+0x8a): undefined reference to `__rela_iplt_start'
/usr/lib/gcc/x86_64-redhat-linux/4.4.2/../../../../lib64/libc.a(elf-init.o):
In function `__libc_csu_init':
(.text+0x98): undefined reference to `__rela_iplt_start'
/usr/lib/gcc/x86_64-redhat-linux/4.4.2/../../../../lib64/libc.a(elf-init.o):
In function `__libc_csu_init':
(.text+0x9e): undefined reference to `__rela_iplt_start'
/usr/lib/gcc/x86_64-redhat-linux/4.4.2/../../../../lib64/libc.a(elf-init.o):
In function `__libc_csu_init':
(.text+0xa3): undefined reference to `__rela_iplt_start'
collect2: ld returned 1 exit status
KSYM .tmp_kallsyms1.S
nm: '.tmp_vmlinux1': No such file
Anyone from redhat who understands the changes to the linker/static libs
should be able to fix this quickly I would have thought.
Cheers
Antoine
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2009-12-27 13:13 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=4B37595C.8050002@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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