Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_PREFER_STATIC_LIB and LDFLAGS+= -static
Date: Fri, 02 Nov 2012 23:21:58 +0100	[thread overview]
Message-ID: <50944786.4040407@mind.be> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6287244@ex-mb1.corp.adtran.com>

On 11/02/12 18:06, ANDY KENNEDY wrote:
> All,
>
> Near line 302 in package/Makefile.in was added TARGET_LDFLAGS += -static
> to satisfy a request I made a while back.  This really needs to be
> --static so that it filters down through autoconf the correct way.  If
> -static is passed in LDFLAGS, autoconf regularly mishandles this by
> setting a variable then never reconfiguring the package's make system
> to build static.  However, the --static to ld is the same as -static,
> but autoconf does not compare for --static, thus, packages get built as
> desired.

  I don't really understand how it can go wrong...  Can you give an example
of a package with a configure script that handles it the wrong way?

>
> Can someone change this in package/Makefile.in or should I submit a
> dinky patch for this?

  Yes, please submit a patch.

  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

  reply	other threads:[~2012-11-02 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 17:06 [Buildroot] BR2_PREFER_STATIC_LIB and LDFLAGS+= -static ANDY KENNEDY
2012-11-02 22:21 ` Arnout Vandecappelle [this message]
2012-11-05 16:24   ` 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=50944786.4040407@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox