From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [toolchain] Linaro 2012.03 issue
Date: Tue, 17 Apr 2012 15:47:47 +0200 [thread overview]
Message-ID: <4F8D7483.1020902@visionsystems.de> (raw)
In-Reply-To: <87obqqjwvz.fsf@macbook.be.48ers.dk>
> Yegor> Has someone used Linaro 2012.03 for C++ based packages?
> Yegor> Everything compiles so far, but libstdc++.so.6 and libgcc_s.so.1
> Yegor> are missing on target. Following run-time error occurs:
> Yegor> Populating using udev: /lib/udev/udevd: error while loading
> Yegor> shared libraries: libgcc_s.so.1: cannot open shared object file:
> Yegor> No such file or directory
>
> Yes, it was pointed out by Shawn Ferris a few days ago as well:
>
> http://lists.busybox.net/pipermail/buildroot/2012-April/052549.html
>
> I'm waiting for the 2012.04 release to see if this was just a bug in
> 2012.03 or if we need to adjust our ext-toolchain support to handle it.
Thanks. I missed this e-mail. Let's hope Linaro devs will fix this.
Yegor
prev parent reply other threads:[~2012-04-17 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 13:28 [Buildroot] [toolchain] Linaro 2012.03 issue Yegor Yefremov
2012-04-17 13:44 ` Peter Korsgaard
2012-04-17 13:47 ` Yegor Yefremov [this message]
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=4F8D7483.1020902@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=buildroot@busybox.net \
/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