From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/erlang-jiffy: needs -fPIC
Date: Mon, 28 Dec 2020 22:53:25 +0100 [thread overview]
Message-ID: <20201228225325.4f973ae1@windsurf.home> (raw)
In-Reply-To: <20201224101440.3427472-1-fontaine.fabrice@gmail.com>
Hello Fabrice,
On Thu, 24 Dec 2020 11:14:40 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fixes:
> - http://autobuild.buildroot.org/results/9ac6e1bf9eaf922c0b7f869416ec33f40ed3543c
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Thanks for the patch. As usual, I'm kind of interested to understand
since when this is happening, why suddenly we need a fix like this. Is
this following a version bump of this package ?
> + {"(linux|solaris|freebsd|netbsd|openbsd|dragonfly|darwin|gnu)",
> +- "LDFLAGS", "$LDFLAGS $FLTO_FLAG -lstdc++"},
> ++ "LDFLAGS", "$LDFLAGS $FLTO_FLAG -lstdc++ -fPIC"},
It is surprising that only LDFLAGS need to be changed. Indeed, -fPIC is
also needed at *compile* time when compiling each individual object
file, so typically in CFLAGS/CXXFLAGS. Why isn't it needed in CXXFLAGS
here ? Because it's already passed at compile time, but forgotten at
link time ? Or because LDFLAGS are also used by rebar at compile time ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-12-28 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 10:14 [Buildroot] [PATCH 1/1] package/erlang-jiffy: needs -fPIC Fabrice Fontaine
2020-12-28 21:53 ` Thomas Petazzoni [this message]
2020-12-29 9:39 ` Fabrice Fontaine
2020-12-29 9:43 ` Thomas Petazzoni
2020-12-29 10:14 ` Fabrice Fontaine
2021-01-01 10:01 ` Yann E. MORIN
2021-01-01 10:37 ` Thomas Petazzoni
2021-03-02 22:49 ` Arnout Vandecappelle
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=20201228225325.4f973ae1@windsurf.home \
--to=thomas.petazzoni@bootlin.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 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.