From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
Date: Wed, 24 Sep 2014 20:01:54 +0200 [thread overview]
Message-ID: <20140924180154.GH3755@pengutronix.de> (raw)
In-Reply-To: <1961773.jAu9WTbTPG@dabox>
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 have
> > 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 Zynx
> compiling nearly the same Project with a different Kernelconfig /DTB for Altera
> SOC fails with this toolchain !?! The kernel boots but on mounting the rootfs
> it fails to execute any binary?
>
> Compiling the same project with OSELAS.Toolchain-2012.12.1/arm-cortexa9-linux-
> 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="-mcpu=cortex-a9 -mfpu=neon"
> PTXCONF_TARGET_EXTRA_CXXFLAGS="-mcpu=cortex-a9 -mfpu=neon"
> 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=y?
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önig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-09-24 18:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 8:07 Michael Olbrich
2014-05-07 8:41 ` Alexander Dahl
2014-05-07 10:23 ` Michael Olbrich
2014-05-07 11:16 ` Alexander Dahl
2014-05-07 12:15 ` Michael Olbrich
2014-05-07 12:30 ` Bernhard Walle
2014-05-07 14:39 ` Uwe Kleine-König
2014-05-07 13:01 ` Alexander Dahl
2014-05-07 13:08 ` Michael Olbrich
2014-09-24 13:43 ` Tim Sander
2014-09-24 18:01 ` Uwe Kleine-König [this message]
2014-09-26 6:09 ` Tim Sander
2014-09-26 6:46 ` Michael Olbrich
2014-09-29 13:47 ` Tim Sander
2014-09-29 13:56 ` Tim Sander
2014-10-01 13:02 ` Michael Olbrich
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=20140924180154.GH3755@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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