From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/erlang-jiffy: needs -fPIC
Date: Fri, 1 Jan 2021 11:37:28 +0100 [thread overview]
Message-ID: <20210101113728.4af33692@windsurf> (raw)
In-Reply-To: <20210101100153.GI2902@scaer>
Hello,
On Fri, 1 Jan 2021 11:01:53 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> The thing with LTO, is that all files should (but in practice: must) be
> compiled with the same set of options; from the gcc man page:
>
> It is recommended that you compile all the files participating in
> the same link with the same options and also specify those options
> at link time.
>
> and later:
>
> There are some code generation flags preserved by GCC when generating
> bytecodes, as they need to be used during the final link. Currently,
> the following options and their settings are taken from the first
> object file that explicitly specifies them: -fPIC, [...]
>
> So, if one file is compiled with -fPIC, then this is recorded in the .o
> for that file, which gcc notices later when doing the link, and thus all
> files must be -fPIC.
>
> This can be a file compiled by the package itself, or it may come from
> an external (staging) static library.
Ah, this is indeed an interesting explanation, which could explain why
adding it just to LDFLAGS solves the problem.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-01 10:37 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
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 [this message]
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=20210101113728.4af33692@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox