From: Dennis.Herbrich@hytera.de
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libgcrypt fails with arm-1136jfs-linux-gnueabihf-gcc from OSELAS.Toolchain-2012.12.0
Date: Wed, 23 Jan 2013 09:41:07 +0100 [thread overview]
Message-ID: <OF09BCF711.42544D13-ONC1257AFC.002EE399-C1257AFC.002FB542@hytera.de> (raw)
In-Reply-To: <mailman.16720.1358867154.2020.ptxdist@pengutronix.de>
Tim Sander wrote:
> As i know that you guys are looking for testing reports for newer
> toolchains i just post this error here.
> Libgcrypt fails to build, the libgpg error works with objdump and with
file:
> file libgpg-error.so.0.5.0: ELF 32-bit LSB shared object, ARM, version 1
> (SYSV), dynamically linked, not stripped
>
> The same stuff works with a OSELAS.Toolchain-2011.03.1/arm-1136jfs-
> linux-gnueabi toolchain. And yes i double
> checked that i have cleaned the working ptxdist project.
[build output snipped]
"Me, too!"
I had the exact same problem building with a current Xilinx-supplied
toolchain,
which is a CodeSourcery Lite 2011.09-50 toolchain for armv7 based on GCC
4.6.1,
with ptxdist-2013.01.0. Since I didn't need that package, I simply made a
note
to try the current OSELAS toolchain later to see if it's reproducable.
"Good to hear" that this would likely not have helped, and there's
possibly an
issue with the package itself. My best guess right now would be a mixed up
order
of (or missing) libraries in the linking stage, but I didn't bother diving
into
the Makefile as of yet.
Regards,
Dennis
--
ptxdist mailing list
ptxdist@pengutronix.de
next parent reply other threads:[~2013-01-23 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16720.1358867154.2020.ptxdist@pengutronix.de>
2013-01-23 8:41 ` Dennis.Herbrich [this message]
2013-01-23 9:33 ` Tim Sander
2013-01-23 11:10 ` Michael Olbrich
2013-01-23 13:39 ` Tim Sander
2013-01-22 15:05 Tim Sander
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=OF09BCF711.42544D13-ONC1257AFC.002EE399-C1257AFC.002FB542@hytera.de \
--to=dennis.herbrich@hytera.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