mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Tim Sander <tim@krieglstein.org>
To: ptxdist@pengutronix.de
Subject: [ptxdist] glibc error with arm-1136jfs-linux-gnueabihf
Date: Thu, 24 Jan 2013 00:10:41 +0100	[thread overview]
Message-ID: <201301240010.41601.tim@krieglstein.org> (raw)

Hi

Here is another error when installing glibc with the 
OSELAS.Toolchain-2012.12.0/arm-1136jfs-linux-gnueabihf toolchain in 
glibc.targetinstall it complains about
install_copy_toolchain_lib: ld-linux.so.3 not found
make: *** [/home/sander/speedy/newToolchain/ptx/platform-pmx-
one/state/glibc.targetinstall] Error 1

Which seems to come from glibc.make:
ifdef PTXCONF_GLIBC_LD
    @$(call install_copy_toolchain_dl, glibc)
endif

But it seems its looking for the wrong file in the toolchain:
/opt/OSELAS.Toolchain-2012.12.0/arm-1136jfs-linux-gnueabihf/gcc-4.7.2-
glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/sysroot-arm-1136jfs-linux-
gnueabihf/lib/ld-2.16.so
/opt/OSELAS.Toolchain-2012.12.0/arm-1136jfs-linux-gnueabihf/gcc-4.7.2-
glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/sysroot-arm-1136jfs-linux-
gnueabihf/lib/ld-linux-armhf.so.3

As i think its the latter it should be either without armhf in the toolchain 
or the install_copy_toolchain_dl magic should do the *right* thing?

Best regards
Tim

-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2013-01-23 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 23:10 Tim Sander [this message]
2013-01-24  7:40 ` Michael Olbrich
2013-01-25 15:34   ` Tim Sander
2013-01-25 16:40     ` Michael Olbrich
2013-01-29  8:29       ` 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=201301240010.41601.tim@krieglstein.org \
    --to=tim@krieglstein.org \
    --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