From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch] Allow file to be built against static libs.
Date: Tue, 19 Jul 2011 23:01:49 +0200 [thread overview]
Message-ID: <87oc0q2ddu.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <87sjq22f6n.fsf@macbook.be.48ers.dk> (Peter Korsgaard's message of "Tue, 19 Jul 2011 22:22:56 +0200")
>>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:
>>>>> "ANDY" == ANDY KENNEDY <ANDY.KENNEDY@adtran.com> writes:
ANDY> If selected "prefer static libs", file fails to build reporting:
ANDY> relocation R_X86_64_32S against `zcalloc' can not be used when making
ANDY> a shared object; recompile with -fPIC
ANDY> The suggested -fPIC doesn't work. The issue is that the default
ANDY> configure has --enable-shared --enable-static. This patch modifies
ANDY> the configure to disable shared when "prefer static libs" is selected.
ANDY> FILE_DEPENDENCIES = host-file zlib
ANDY> HOST_FILE_DEPENDENCIES = host-zlib
ANDY> +ifeq ($(BR2_PREFER_STATIC_LIB),y)
ANDY> +FILE_CONF_OPT = --disable-shared --enable-static
ANDY> +HOST_FILE_CONF_OPT = --disable-shared --enable-static
Peter> We indeed force --enable-shared --disable-static for host builds, but
Peter> that doesn't really matter. For target builds we use (see
Peter> package/Makefile.in) --enable-static --enable-shared when
Peter> PREFER_STATIC_LIB is enabled, so rather than something file specific, I
Peter> think it would make more sense to set that to --enable-static
Peter> --disable-shared instead.
Ehh, drop that, I remembered wrong - We're already doing --enable-static --disable-shared.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-07-19 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 19:48 [Buildroot] [Patch] Allow file to be built against static libs ANDY KENNEDY
2011-07-19 20:22 ` Peter Korsgaard
2011-07-19 20:42 ` Thomas Petazzoni
2011-07-19 21:01 ` Peter Korsgaard [this message]
2011-07-20 4:53 ` ANDY KENNEDY
2011-07-20 21:51 ` Peter Korsgaard
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=87oc0q2ddu.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.