From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lzop: unbreak powerpc build with GCC >= 5
Date: Fri, 30 Sep 2016 10:06:19 +0200 [thread overview]
Message-ID: <87vaxdyfpg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160928143314.16109-1-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 28 Sep 2016 16:33:14 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes:
> http://autobuild.buildroot.net/results/c60/c60554f7b84d5050b86c1735fb857856ddfa4dff/
> http://autobuild.buildroot.net/results/888/888ea1aea200a71d0887754e2afabdc6b260bf2f/
> http://autobuild.buildroot.net/results/219/219194d269d7f3cf4c3db120e6d8079085916bd3/
> GCC >= 5 changed the behaviour of 'extern inline', causing linking errors
> when the powerpc inline functions are used in multiple compilation units:
> https://gcc.gnu.org/gcc-5/porting_to.html
> Add a patch from openembedded to change it to use static inline (which has
> the correct behaviour in both old/new GCC versions) to fix it.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Venlig hilsen,
Peter Korsgaard
prev parent reply other threads:[~2016-09-30 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 14:33 [Buildroot] [PATCH] lzop: unbreak powerpc build with GCC >= 5 Peter Korsgaard
2016-09-30 8:06 ` Peter Korsgaard [this message]
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=87vaxdyfpg.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