From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 16 Nov 2016 23:53:09 +0100 Subject: [Buildroot] [PATCH 1/1] sdl: fix building on powerpc64 and powerpc64le In-Reply-To: <20161116224950.GA2559@tungsten.ozlabs.ibm.com> References: <20161107225106.5e9e61b6@free-electrons.com> <53f345eb-3ea1-02ef-06bf-72f011b3728a@mind.be> <20161108051006.GB6803@tungsten.ozlabs.ibm.com> <99a8adb3-3fa3-7050-e31f-16d2ee67ea12@mind.be> <20161109043021.GA10982@tungsten.ozlabs.ibm.com> <20161116123331.44f50097@free-electrons.com> <20161116224950.GA2559@tungsten.ozlabs.ibm.com> Message-ID: <20161116235309.094f6d15@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Thu, 17 Nov 2016 09:49:50 +1100, Sam Bobroff wrote: > > 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 :-) Great! > 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. OK. Arnout has also posted a great summary of the possible solutions. It's great to have the info that about 10% of the packages seem to be affected, this sort of number can help in choosing between the different options we have. > However, I've also run into several failures that are different issues, > so this isn't going to fix them all. Sure, that's expected and perfectly OK. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com