From: Sam Bobroff <sam.bobroff@au1.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] sdl: fix building on powerpc64 and powerpc64le
Date: Thu, 17 Nov 2016 09:49:50 +1100 [thread overview]
Message-ID: <20161116224950.GA2559@tungsten.ozlabs.ibm.com> (raw)
In-Reply-To: <20161116123331.44f50097@free-electrons.com>
On Wed, Nov 16, 2016 at 12:33:31PM +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Sun, 13 Nov 2016 21:18:46 +0100, Arnout Vandecappelle wrote:
>
> > Nice idea, but it's only possible for internal toolchains. Unless if we merge
> > the ld-wrapper patches (last news of which was: it shouldn't be needed).
> >
> > I'm slightly inclined to go for patching configure or libtool.m4 instead.
>
> Can we move forward with this topic? Could somone summarize the problem
> and options we have with advantages/drawbacks?
>
> We've got quite a lot of build failures because of that. In the latest
> autobuild report, we've got 7 build failures on powerpc64le (on a total
> of 41 build failures), and I suspect a significant number of them are
> due to this libtool issue.
Sorry I've been quiet but I've been working on this :-)
I've built and used scripts to scan about 1,000 packages, and it looks
like about 100 of them have this problem. I'll post an RFC patch shortly
and answer your questions, above.
However, I've also run into several failures that are different issues,
so this isn't going to fix them all.
Cheers,
Sam.
next prev parent reply other threads:[~2016-11-16 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 3:29 [Buildroot] [PATCH 1/1] sdl: fix building on powerpc64 and powerpc64le Sam Bobroff
2016-11-07 21:51 ` Thomas Petazzoni
2016-11-08 1:04 ` Arnout Vandecappelle
2016-11-08 5:10 ` Sam Bobroff
2016-11-08 12:24 ` Arnout Vandecappelle
2016-11-09 4:30 ` Sam Bobroff
2016-11-13 17:13 ` Bernd Kuhls
2016-11-13 20:18 ` Arnout Vandecappelle
2016-11-16 11:33 ` Thomas Petazzoni
2016-11-16 22:42 ` Arnout Vandecappelle
2016-11-18 0:22 ` Sam Bobroff
2016-11-16 22:49 ` Sam Bobroff [this message]
2016-11-16 22:53 ` Thomas Petazzoni
2016-11-08 3:44 ` Sam Bobroff
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=20161116224950.GA2559@tungsten.ozlabs.ibm.com \
--to=sam.bobroff@au1.ibm.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