Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libcap: fix static linking issue
Date: Sun, 13 Oct 2013 21:44:08 +0200	[thread overview]
Message-ID: <525AF808.4000207@openwide.fr> (raw)
In-Reply-To: <20131008101327.5ee7cc9c@skate>

Hi,

Le 08/10/2013 10:13, Thomas Petazzoni a ?crit :
> Dear Romain Naour,
> 
> On Tue, 8 Oct 2013 10:11:53 +0200 (CEST), Romain Naour wrote:
> 
>> | > +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.
>>
>> Ok, I'll take the problem from the beginning.
>> Sorry for that mistake.
> 
> Note that I'm not sure about what I said, but having to build with
> -fPIC in the static lib case seems really strange.
> 
> Thanks!
> 
> Thomas
> 

You're right, the static lib isn?t built with -fPIC.
But the libcap build system build the static and shared libraries,
even if you don't want one of them.

The build failure [1] is caused by the missing -fPIC during the build of libcap.so.2.22

So, we may add -fPIC if BR2_PREFER_STATIC_LIB=y and the shared lib is build correctly
(ok it's weird)
Or add a patch for enable/disable separately the static/shared build.

Best regards,
Romain Naour

[1] http://autobuild.buildroot.net/results/619bceb3491ecd2ed4e1ae552fdb237a0ed2fa47/

  reply	other threads:[~2013-10-13 19:44 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
2013-10-08  8:11   ` Romain Naour
2013-10-08  8:13     ` Thomas Petazzoni
2013-10-13 19:44       ` Romain Naour [this message]
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=525AF808.4000207@openwide.fr \
    --to=romain.naour@openwide.fr \
    --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