From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/4] libgmp: fix issue with missing -fPIC
Date: Fri, 21 Mar 2014 09:55:50 +0100 [thread overview]
Message-ID: <20140321085548.GB25178@omega> (raw)
In-Reply-To: <20140321083145.GJ23331@pengutronix.de>
On Fri, Mar 21, 2014 at 09:31:45AM +0100, Michael Olbrich wrote:
> On Fri, Mar 21, 2014 at 09:04:21AM +0100, Alexander Aring wrote:
> > While compiling nettle which depends on libgmp I got the following
> > linking error:
> >
> > .../sysroot-target/usr/lib/libgmp.a(mp_get_fns.o): relocation
> > R_ARM_THM_MOVW_ABS_NC against `__gmp_allocate_func' can not be used when
> > making a shared object; recompile with -fPIC
> > .../sysroot-target/usr/lib/libgmp.a: error adding symbols: Bad value
> >
> > This patch adds a "--with-pic" to the configure argument to solve this
> > problem.
>
> I'd rather you remove the LIBGMP_STATIC option. The shared library is
> always PIC.
>
Yea, that would be the alternative. I thought maybe there exist some
other non mainline rules which need a static and not a shared lib.
Okay, then I drop the static lib thing and always build a shared library
this will make the world much easier.
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-03-21 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 8:04 Alexander Aring
2014-03-21 8:04 ` [ptxdist] [PATCH 2/4] libgmp: add missing with-gnu-ld Alexander Aring
2014-03-21 8:34 ` Michael Olbrich
2014-03-21 8:53 ` Alexander Aring
2014-03-21 8:04 ` [ptxdist] [PATCH 3/4] libgmp: remove targetinstall of static lib Alexander Aring
2014-03-21 8:04 ` [ptxdist] [PATCH 4/4] libgmp: remove LIBGMP_STATIC menu entry Alexander Aring
2014-03-21 8:33 ` Michael Olbrich
2014-03-21 8:31 ` [ptxdist] [PATCH 1/4] libgmp: fix issue with missing -fPIC Michael Olbrich
2014-03-21 8:55 ` Alexander Aring [this message]
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=20140321085548.GB25178@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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