From: Mathieu Lacage <mathieu.lacage@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: building non-shared dynamic binaries on x86-64 linux-elf
Date: Wed, 22 Apr 2009 11:57:00 -0000 [thread overview]
Message-ID: <74fef6df0904220457y5650ab4eq215fe274badf60f4@mail.gmail.com> (raw)
hi,
The title pretty much says what I am trying to do: this works fine on
i386 but fails on x86-64. The compile-time error is:
"relocation R_X86_64_32 against `a local symbol' can not be used when
making a shared object; recompile with -fPIC".
What I am trying to do is generate a non-shared relocatable dynamic
binary which means that I really don't want to use -fPIC and I was
hoping that the dynamic linker would be able to finish relocating the
final binary. Is this impossible on linux-elf-x86-64 ?
Mathieu
--
Mathieu Lacage <mathieu.lacage@gmail.com>
next reply other threads:[~2009-04-22 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 11:57 Mathieu Lacage [this message]
2009-04-22 12:00 ` Andrew Haley
2009-04-22 13:32 ` Ian Lance Taylor
2009-04-22 14:44 ` Mathieu Lacage
2009-04-22 14:51 ` Ian Lance Taylor
2009-04-22 14:53 ` Andrew Haley
2009-04-22 15:20 ` Mathieu Lacage
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=74fef6df0904220457y5650ab4eq215fe274badf60f4@mail.gmail.com \
--to=mathieu.lacage@gmail.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).