mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Antwort: Re: [ANNOUNCE] OSELAS.Toolchain() 2012.12.0 released
Date: Thu, 20 Dec 2012 14:28:03 +0100	[thread overview]
Message-ID: <20121220132803.GA23720@pengutronix.de> (raw)
In-Reply-To: <80D5C4B7-623C-4B4D-BEC9-A7F82A2465D2@etit.tu-chemnitz.de>

On Thu, Dec 20, 2012 at 01:47:34PM +0100, Daniel Kriesten wrote:
> Hardfloat leads me to the next question:
> 
> I build a Raspberry Pi hf-toolchain, where ld-linux.so.3 is named
> ld-linux-armhf.so.3. This leads to an error in the target install of glibc.
> 
> Do I need to fix my toolchain config or the install_lib function?

No, this is a Bug in the toolchain. I've tried the same thing a few days
ago. This is a problem with gcc-4.7.x. It was fixed in the 4.8 branch and
Linaro back-ported it for its own releases. So only
arm-1136jfs-linux-gnueabihf is affected.  I've pushed a fix to the
toolchain git repository[1]. It will be fixed in the next bugfix release.

Michael

[1] git://git.pengutronix.de/git/OSELAS.Toolchain.git

-- 
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

  reply	other threads:[~2012-12-20 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 18:27 [ptxdist] " Michael Olbrich
2012-12-20 12:10 ` Bernhard Walle
2012-12-20 12:27   ` [ptxdist] Antwort: " Robert Bouwens
2012-12-20 12:37     ` Bernhard Walle
2012-12-20 12:47       ` Daniel Kriesten
2012-12-20 13:28         ` Michael Olbrich [this message]
2012-12-20 13:10       ` Robert Schwebel
2012-12-20 13:53     ` 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=20121220132803.GA23720@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