Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] BR2_PREFER_STATIC_LIB and LDFLAGS+= -static
Date: Tue, 6 Nov 2012 08:14:10 +0100	[thread overview]
Message-ID: <20121106081410.4aa94df3@skate> (raw)
In-Reply-To: <50984D57.3080402@mind.be>


On Tue, 06 Nov 2012 00:35:51 +0100, Arnout Vandecappelle wrote:

>   Although I'm OK with this patch, I have been unable to reproduce the problem
> and I'd like to know why it is going wrong with -static.  Can you post a
> defconfig that I can rebuild and that exposes the problem?

Yes, I also would like more details about why this is needed. I think
the TARGET_LDFLAGS thing is currently quite confusing: some packages
are using it as flags for gcc at the link stage, some other packages
are using it as flags for ld directly. Maybe this is what should be
clarified somehow?

>   Note: a few autobuilders with BR2_PREFER_STATIC_LIB enabled could be nice -
> or maybe not, because many packages _will_break.

I intended to make my autobuilder script randomly select
BR2_PREFER_STATIC_LIB, BR2_CCACHE and a few other "big" options, but
until now, I had the feeling that the autobuilder results already
provided enough failures to keep us busy :-)

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-11-06  7:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 16:55 [Buildroot] [PATCH] BR2_PREFER_STATIC_LIB and LDFLAGS+= -static ANDY KENNEDY
2012-11-05 23:35 ` Arnout Vandecappelle
2012-11-06  7:14   ` Thomas Petazzoni [this message]
2012-11-06 15:06   ` ANDY KENNEDY
2012-11-06 22:32     ` Arnout Vandecappelle
2013-01-14 18:51 ` [Buildroot] [PATCH][poke] " ANDY KENNEDY
2013-01-14 19:36   ` Peter Korsgaard
2013-01-14 19:39     ` ANDY KENNEDY

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=20121106081410.4aa94df3@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