From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Wed, 24 Sep 2014 20:01:54 +0200 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Message-ID: <20140924180154.GH3755@pengutronix.de> References: <20140507080758.GA17823@pengutronix.de> <1961773.jAu9WTbTPG@dabox> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1961773.jAu9WTbTPG@dabox> Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Michael Olbrich On Wed, Sep 24, 2014 at 03:43:10PM +0200, Tim Sander wrote: > Hi > = > > I'm happy to announce that I've just released OSELAS.Toolchain-2013.12.= 2. > > = > > This is a bugfix-only release. The relevant changes since 2013.12.1 are: > > - The toolchains can now be built with make 4.0 > > - Some toolchains did not optimize for the correct CPU. The code works= but > > might be slower. This is fixed now. > > - All security relevant fixes mentioned in the glibc 2.19 changelog ha= ve > > been added for glibc 2.18 based toolchains. > > - All generated toolchain archives are now XZ comressed. > While i have used this toolchain arm-v7a-linux-gnueabihf with an Xilinx Z= ynx = > compiling nearly the same Project with a different Kernelconfig /DTB for = Altera = > SOC fails with this toolchain !?! The kernel boots but on mounting the ro= otfs > it fails to execute any binary? > = > Compiling the same project with OSELAS.Toolchain-2012.12.1/arm-cortexa9-l= inux- > gnueabihf/gcc-4.7.3-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized does = work = > however. = > = > I have also tried setting: > PTXCONF_TARGET_EXTRA_CFLAGS=3D"-mcpu=3Dcortex-a9 -mfpu=3Dneon" > PTXCONF_TARGET_EXTRA_CXXFLAGS=3D"-mcpu=3Dcortex-a9 -mfpu=3Dneon" > But it still fails on executing any binary. Without knowing details about the two toolchains in question, this might be an ABI-problem. Does your kernel have OABI_COMPAT=3Dy? Did you try to run a 2013.12.1 userspace with a 2012.12.1-compiled kernel and vice versa? Best regards Uwe -- = Pengutronix e.K. | Uwe Kleine-K=F6nig | Industrial Linux Solutions | http://www.pengutronix.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de