From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2,1/1] gnuchess: needs -fPIC
Date: Mon, 04 Feb 2019 18:55:34 +0100 [thread overview]
Message-ID: <87h8djtp49.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <391d5d2d-90ca-1224-ce6f-cab3b440cbc7@mind.be> (Arnout Vandecappelle's message of "Wed, 23 Jan 2019 15:21:18 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>> I'm sorry but this doesn't make sense to me. -fPIC is for Position
>> Independent Code, which is needed when building shared libraries. Here
>> we are building with -static on Cortex-M which doesn't even have
>> support for shared libraries. So building with -fPIC doesn't make sense
>> I believe. It seems to be more a workaround than a real fix.
>>
>> Perhaps this should be discussed with upstream binutils, or at least a
>> proper investigation be done about those relocation types ?
> Or we could argue that gnuchess on Cortex-M probably isn't that essential, and
> just put an architecture dependency...
That is also OK with me.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-02-04 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 17:55 [Buildroot] [PATCH v2,1/1] gnuchess: needs -fPIC Fabrice Fontaine
2019-01-13 13:13 ` Thomas Petazzoni
2019-01-23 14:21 ` Arnout Vandecappelle
2019-02-04 17:55 ` Peter Korsgaard [this message]
2019-06-23 18:23 ` Thomas Petazzoni
2019-06-25 21:04 ` Peter Korsgaard
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=87h8djtp49.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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