From: Michael Olbrich <m.olbrich@pengutronix.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 12:10:42 +0100 [thread overview]
Message-ID: <20130123111042.GC26180@pengutronix.de> (raw)
In-Reply-To: <5116852.yDijcSoVCo@dabox>
Hi,
On Wed, Jan 23, 2013 at 10:33:52AM +0100, Tim Sander wrote:
> > 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.
> I first thought it would be a hardfloat toolchain problem. But this problem also
> occurs with the arm-1136jfs-linux-gnueabi toolchain same version. So yep it
> seems to be a problem of the packet.
This is a bug in libgcrypt that is exposed by a change in binutils:
ac-schemes.o: undefined reference to symbol 'gpg_err_code_from_errno'
ac-schemes uses gpg_err_code_from_errno() but only links to libgcrypt.so
explicitly.
The old bahaviour was like this: libgcrypt.so links to libgpg-error.so.0,
so libgpg-error.so.0 is also used if needed.
With the new behaviour only explicitly specified libs are used, resulting
in this error.
The old behaviour can be restored by adding "-WL,--copy-dt-needed-entries"
to the ldflags (PTXCONF_TARGET_EXTRA_LDFLAGS in the platformconfig).
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-01-23 11:10 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
2013-01-23 9:33 ` Tim Sander
2013-01-23 11:10 ` Michael Olbrich [this message]
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=20130123111042.GC26180@pengutronix.de \
--to=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