From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: make the shared library optional
Date: Fri, 07 Nov 2014 15:16:10 +0100 [thread overview]
Message-ID: <1415369770.19702.30.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 54579526.5080003@imgtec.com
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
On Mon, 2014-11-03 at 14:45 +0000, Vicente Olivert Riera wrote:
> I'm having a failure when doing a static build of elfutils because it
> tries to build a shared library (.so). Could it be possible to add a
> configure option to disable the shared library so only the static one
> (.a) would be built?
>
> This is the failure I'm talking about:
>
> /home/chroot/media/code/buildroot/autobuilder/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/mipsel-buildroot-linux-uclibc/4.8.3/../../../../mipsel-buildroot-linux-uclibc/bin/ld:
> /home/chroot/media/code/buildroot/autobuilder/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/mipsel-buildroot-linux-uclibc/4.8.3/crtbeginT.o:
> relocation R_MIPS_HI16 against `a local symbol' can not be used when
> making a shared object; recompile with -fPIC
> /home/chroot/media/code/buildroot/autobuilder/instance-0/output/host/opt/ext-toolchain/bin/../lib/gcc/mipsel-buildroot-linux-uclibc/4.8.3/crtbeginT.o:
> could not read symbols: Bad value
> collect2: error: ld returned 1 exit status
> Makefile:939: recipe for target 'libelf.so' failed
> make[3]: *** [libelf.so] Error 1
Does that failure also happen with a normal (not patched) build?
It looks like the issue is with the crtbeginT.o code, not with any of
the elfutils objects? I don't immediately know why that particular
object is linked into the shared library. Does the toolchain pick up the
correct version?
> The full build log is here:
>
> http://autobuild.buildroot.net/results/16f/16f6956d5a215fe678a45cc4b24ba196309ee05c/build-end.log
It looks like that is a fairly old 0.155 build with several patches
applied. Have you tried latest elfutils 0.160 or current git?
If you think any of those patches are useful could you submit them so we
can review them for inclusion upstream?
Thanks,
Mark
next reply other threads:[~2014-11-07 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 14:16 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-11 9:11 Mark Wielaard
2014-11-10 16:49 Vicente Olivert Riera
2014-11-08 15:14 Mark Wielaard
2014-11-07 16:27 Vicente Olivert Riera
2014-11-07 15:47 Vicente Olivert Riera
2014-11-05 13:32 Vicente Olivert Riera
2014-11-04 17:01 Petr Machata
2014-11-03 14:45 Vicente Olivert Riera
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=1415369770.19702.30.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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).