From: jean-philippe francois <jp.francois@cynove.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Building non multilib platform with multilib toolchain
Date: Wed, 3 Oct 2012 13:10:16 +0200 [thread overview]
Message-ID: <CAGGh5h0dkDO5K+hJMoX7=L9fCdR0nFQhGvZ=u6bXNHoOG0pNkQ@mail.gmail.com> (raw)
Hi,
a non multilib toolchain (code sourcery example) is layed out like
this in my experience :
/arm-none-linux-gnueabi/libc/lib/ contains all the .so
while a multilib toolchain layout is different (last linaro toolchains)
/arm-linux-gnueabihf/libc/lib contains :
/arm-linux-gnueabi/
/arm-linux-gnueabihf/
ld-linux-armhf.so.3 -> ld.so in hf subdir
ld-linux.so ->ld.so in softfloat subdir
This leads me to two question :
1) This is not ptxdist related, but is it possible
to build a monolib system and use one of the multilib subdir
as the lib directory, or eventually keep the layout but remove for example
arm-linux-gnueabi
2) do 1 with ptxdist ?
Currently, glibc-target-install fails with
link - /home/cynove/bin/arm-linaro-2012.09/arm-linux-gnueabihf/libc/lib/ld-linux-armhf.so.3
lib - /home/cynove/bin/arm-linaro-2012.09/arm-linux-gnueabihf/libc/lib/arm-linux-gnueabihf/ld-2.15.so
ptxdist: error: cannot identify prefix and no user supplied dest
Regards,
Jean-Philippe Francois
--
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2012-10-03 11:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGGh5h0dkDO5K+hJMoX7=L9fCdR0nFQhGvZ=u6bXNHoOG0pNkQ@mail.gmail.com' \
--to=jp.francois@cynove.com \
--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