From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 5 Jul 2013 11:21:22 +0200 Subject: [Buildroot] Antw:Re: libgcc build fails on Fedora15 In-Reply-To: <1373015044930-47930.post@n4.nabble.com> References: <7290940beabd3.4e7df687@home.nl> <20110924174825.131f8fee@skate> <72a087c6ebedc.4e7e366e@home.nl> <1373015044930-47930.post@n4.nabble.com> Message-ID: <20130705112122.60b12a22@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Ian Eperson, On Fri, 5 Jul 2013 02:04:04 -0700 (PDT), Ian Eperson wrote: > Was there any resolution, or even progress, on the (apparent) legacy > Fedora:Buildroot incompatibility? > > I am getting the same error (libgcc_s.so.1: ELF file OS ABI invalid) across > a variety of Buildroots from 2009, 2010, 2011 with Fedora Core 16. > > Any guidance would be useful. Is moving Fedora forward or back likely to > overcome this (or moving to some other development platform)? Would moving > forward or back with Buildroot be a better strategy? > > The target is for a mature Atmel ARM9 SOC. The assumption was that > (roughly) aligning the platform, target and Buildroot versions in time was > likely to maximize compatibility. Clearly not. I've started a download of a Fedora Core 16 VirtualBox image to be able to test this and see if I can reproduce. Can you share your Buildroot .config, and tell us if the problem also happens with more recent Buildroot versions? Thanks, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com