From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: [PATCH 1/1] uboot: Strip "-Wl," from LDFLAGS
Date: Fri, 3 Jun 2016 16:03:42 +0200 [thread overview]
Message-ID: <20160603160342.09e52895@free-electrons.com> (raw)
In-Reply-To: <CANCHnQqhQjhG6EBapYvSODPCXjMFpLZx2AAB4bnUWuJuy4kcKg@mail.gmail.com>
Hello,
On Fri, 3 Jun 2016 16:00:42 +0200, Jeroen Roovers wrote:
> The patch *doesn't* pass LDFLAGS down; GNU make simply picks up the
> exported LDFLAGS from buildroot and integrates it with its own flags.
> I only found out because when I set BR2_TARGET_LDFLAGS using the usual
> GCC flags and did a complete rebuild, I found that only uboot failed
> to build.
Buildroot does not export LDFLAGS, and only passes it down to packages
if it's explicitly done in the package .mk file.
Try the defconfig I posted, it built just fine, even though it has
-Wl,--as-needed in BR2_TARGET_LDFLAGS.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-03 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455102927-28502-1-git-send-email-jer@airfi.aero>
2016-02-10 15:03 ` [Buildroot] Fwd: [PATCH 1/1] uboot: Strip "-Wl," from LDFLAGS Jeroen Roovers
2016-02-10 16:41 ` Thomas Petazzoni
[not found] ` <CANCHnQogKCY-OTT2=wTkNJ8D52QWetBqdnWbfAqRKKcoW8Yrpw@mail.gmail.com>
[not found] ` <CANCHnQp5E4kx=2VpVDXAC-sn+ruxe=0nwamG=DXp_WEgQVCRjw@mail.gmail.com>
2016-02-19 15:04 ` [Buildroot] Fwd: Fwd: [PATCH 1/1] uboot: Strip "-Wl, " " Jeroen Roovers
2016-06-03 13:18 ` [Buildroot] Fwd: [PATCH 1/1] uboot: Strip "-Wl," " Thomas Petazzoni
2016-06-03 14:00 ` Jeroen Roovers
2016-06-03 14:03 ` Thomas Petazzoni [this message]
2016-06-03 14:10 ` Jeroen Roovers
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=20160603160342.09e52895@free-electrons.com \
--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