From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: Fix build failure related to -fPIC for x86_64 -> i686 builds
Date: Mon, 24 Apr 2017 00:06:30 +0200 [thread overview]
Message-ID: <aded779d-fd0d-e83c-5a3e-d0e7b28b5dfe@mind.be> (raw)
In-Reply-To: <71cfdaf7-367d-44de-a1c6-9041e269c8de@cesnet.cz>
On 19-04-17 18:23, Jan Kundr?t wrote:
>> Without this patch, I cannot build the toolchain (both host-gcc-initial
>> and -final) on Gentoo's amd64 using GCC 4.9.3:
>>
>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/../../../../x86_64-pc-linux-gnu/bin/ld:
>> gcov.o: relocation R_X86_64_32 against `.rodata.str1.8' can not
>> be used when making a shared object; recompile with -fPIC
>
> One important piece I forgot to add -- I'm running "Hardened Gentoo GCC" which
> enables PIE by default [1] [2]. As such, this might explain why other are
> (presumably) not seeing this problem.
Indeed. However, I wonder, won't you have a similar problem with other host
packages that try to build something without -fPIC?
We don't like to accept patches where it is not clear what happens, i.e. how
this particular change fixes your problem...
> BTW, I cannot find my original submission on patchwork. Was that e-mail OK? I
> see it in the ML archive [3].
I believe it's because you sent it base64-encoded, patchwork only likes
plaintext. You didn't use git send-email, did you?
Regards,
Arnout
>
> With kind regards,
> Jan
>
> [1]
> https://wiki.gentoo.org/wiki/Hardened/Toolchain#Automatic_generation_of_Position_Independent_Executables_.28PIEs.29
>
> [2]
> https://wiki.gentoo.org/wiki/Hardened/Toolchain#Toolchain_modifications_for_automatic_PIEs
>
> [3] http://lists.busybox.net/pipermail/buildroot/2017-April/189441.html
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-04-23 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 16:23 [Buildroot] [PATCH] gcc: Fix build failure related to -fPIC for x86_64 -> i686 builds Jan Kundrát
2017-04-23 22:06 ` Arnout Vandecappelle [this message]
2017-04-24 11:19 ` Jan Kundrát
2017-04-24 20:21 ` Arnout Vandecappelle
2017-04-25 11:17 ` Jan Kundrát
-- strict thread matches above, loose matches on Subject: below --
2017-04-12 21:09 Jan Kundrát
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=aded779d-fd0d-e83c-5a3e-d0e7b28b5dfe@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