From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] mii-diag: link statically if configured to do so
Date: Sat, 30 Jun 2012 15:02:12 +0200 [thread overview]
Message-ID: <4FEEF8D4.4080702@mind.be> (raw)
In-Reply-To: <20120630105559.7e57508a@skate>
On 06/30/12 10:55, Thomas Petazzoni wrote:
> Le Sat, 30 Jun 2012 10:32:14 +0200,
> Peter Korsgaard<jacmet@uclibc.org> a ?crit :
>
>> Thomas> I am not fully sure I like this. Do we want to have the same
>> Thomas> stuff in all packages, or should we think about doing this
>> Thomas> globally in some way?
>>
>> Agree, I've added it globally now.
>
> Yes, seen that, great. Does this addition of -static to TARGET_LDFLAGS
> play well with --enable-static for AUTOTARGETS packages?
--enable-static should mean that static libraries should be built,
while -static says that the executable should only be linked with
static libraries. But of course, with all the non-standard autotools
stuff out there, you never know...
I expect that adding -static to LDFLAGS will break quite a few packages.
Would it be possible to add a BR2_PREFER_STATIC_LIB test to the autobuilds?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-06-30 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 20:03 [Buildroot] [git commit] mii-diag: link statically if configured to do so Peter Korsgaard
2012-06-29 10:16 ` Thomas Petazzoni
2012-06-29 11:23 ` Jonas Keidel
2012-06-30 8:32 ` Peter Korsgaard
2012-06-30 8:55 ` Thomas Petazzoni
2012-06-30 13:02 ` Arnout Vandecappelle [this message]
2012-06-30 17:09 ` Alex Bradbury
2012-07-03 17:56 ` Thomas Petazzoni
2012-07-03 19:08 ` Peter Korsgaard
2012-06-30 22:01 ` Peter Korsgaard
2012-07-01 19:32 ` Thomas Petazzoni
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=4FEEF8D4.4080702@mind.be \
--to=arnout@mind.be \
--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.