From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Raz <raziebe@gmail.com>
Subject: Re: [ptxdist] libstd++.so.6 is not copied
Date: Tue, 17 Sep 2013 16:31:19 +0200 [thread overview]
Message-ID: <201309171631.19511.jbe@pengutronix.de> (raw)
In-Reply-To: <CAPB=Z-r6yUvghTKY-0z0CYe5eNRNPPoy7zvzTFwFhQ3nwz4PcQ@mail.gmail.com>
On Sunday 15 September 2013 16:41:45 Raz wrote:
> I am using OSELAS 2012.12.1 with toolchain 2012.12.1
> When I build libstdc++.so.6 is not copied even though
> libstdc++.so does. same applies for libm.s0.6 and libresolve.so.0
Did you copy your toolchain form one machine to a different one? The behaviour
you see happens if libstdc++.so is a file and not a link. And if you copy the
toolchain some tools replace the links with real files.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-09-17 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 14:41 Raz
2013-09-17 14:31 ` Jürgen Beisert [this message]
2013-09-19 19:32 ` Raz
2013-09-20 9:16 ` Jürgen Beisert
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=201309171631.19511.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=raziebe@gmail.com \
/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