From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libcap: fix static linking issue
Date: Sun, 6 Oct 2013 23:29:54 +0200 [thread overview]
Message-ID: <20131006232954.71da4d75@skate> (raw)
In-Reply-To: <5251C3B0.7090105@openwide.fr>
Dear Romain Naour,
On Sun, 06 Oct 2013 22:10:24 +0200, Romain Naour wrote:
> Add -fPIC flag
>
> Fixes:
> http://autobuild.buildroot.net/results/619bceb3491ecd2ed4e1ae552fdb237a0ed2fa47/
>
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> ---
> package/libcap/libcap.mk | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/package/libcap/libcap.mk b/package/libcap/libcap.mk
> index 16afaef..6248fed 100644
> --- a/package/libcap/libcap.mk
> +++ b/package/libcap/libcap.mk
> @@ -25,10 +25,15 @@ endif
> # we don't have host-attr
> HOST_LIBCAP_DEPENDENCIES =
>
> +ifeq ($(BR2_PREFER_STATIC_LIB),y)
> +LIBCAP_LDFLAGS=-fPIC
> +endif
This seems really weird, because normally, we would expect exactly the
opposite: position independent code is needed for shared libraries, not
for static libraries.
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-06 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 20:10 [Buildroot] [PATCH 1/1] libcap: fix static linking issue Romain Naour
2013-10-06 21:29 ` Thomas Petazzoni [this message]
2013-10-08 8:11 ` Romain Naour
2013-10-08 8:13 ` Thomas Petazzoni
2013-10-13 19:44 ` Romain Naour
2013-10-16 16:09 ` Thomas Petazzoni
2013-11-01 17:48 ` Thomas Petazzoni
2013-11-02 15:52 ` Romain Naour
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=20131006232954.71da4d75@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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