public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2251] Weak undefined symbol doesn't work properly with PIE Date: Tue, 31 Jan 2006 19:17:00 -0000 [thread overview] Message-ID: <20060131191711.2791.qmail@sourceware.org> (raw) In-Reply-To: <20060131191328.2251.hjl@lucon.org> ------- Additional Comments From hjl at lucon dot org 2006-01-31 19:17 ------- Created an attachment (id=854) --> (http://sourceware.org/bugzilla/attachment.cgi?id=854&action=view) A testcase PIE built with the fixed linker, I got gcc -B./ -c -fPIC -g bar.c gcc -B./ -shared -o libbar.so bar.o #-z nocombreloc gcc -B./ -c -fPIC -g foo.c gcc -B./ -c -fPIC -g main.c gcc -B./ -c -fPIC -g dummy.c gcc -B./ -shared -o libdummy.so dummy.o #-z nocombreloc gcc -B./ -pie -o pie foo.o main.o libdummy.so -Wl,-z,nocombreloc -Wl,-rpath,. gcc -B./ -o exec foo.o main.o libdummy.so -Wl,-z,nocombreloc -Wl,-rpath,. cp -af libbar.so libdummy.so ./exec main foo PASSED ./pie main foo FAILED That is undefined weak symbol in PIE is resolved to a definition in libdummy.so unlike the normal executable. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2251 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-01-31 19:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-31 19:13 [Bug libc/2251] New: " hjl at lucon dot org 2006-01-31 19:17 ` hjl at lucon dot org [this message] 2006-01-31 19:40 ` [Bug libc/2251] " hjl at lucon dot org 2006-02-01 13:50 ` vapier at gentoo dot org 2006-03-01 3:57 ` vapier at gentoo dot org 2006-03-30 3:20 ` bje at sources dot redhat dot com 2006-08-09 6:07 ` drepper at redhat dot com
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=20060131191711.2791.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).