From: glscantlen <glscantlen@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] build libstdc++.so.6
Date: Wed, 22 Jul 2015 09:56:13 -0700 (PDT) [thread overview]
Message-ID: <1437584173498-106871.post@n4.nabble.com> (raw)
In-Reply-To: <20150712002830.018e4bc0@free-electrons.com>
Thanks for reply Thomas,
I have no good reason for using that version of their toolchain.
I did find an earlier version of eglibc binary that contained stdc++.
sysroot-linaro-eglibc-gcc4.9-2014.11-arm-linux-gnueabihf.tar.xz
But I have not tried that ver. yet.
My biggest concern is having to rebuild any toolchain after a
' make clean' in Buildroot. I am sure there are other methods to
over come a toolchain rebuild, I just have not found one I like.
I am currently using a hack, copy from an Ubuntu build for arm.
And I only need the shared stdc++ for libmali.so which was
also a copy from the same Ubuntu build. I would prefer to build
libmali.so using the provided static stdc++ BUT! libmali source
contains proprietary code provided thru ARM commercial licence
and I have not yet resolved THAT issue. See this site:
http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-linux-exadri2-and-x11-display-drivers/
Thanks again
Gary
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/build-libstdc-so-6-with-custom-toolchain-Linaro-4-9-tp105322p106871.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2015-07-22 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 17:03 [Buildroot] build libstdc++.so.6 glscantlen
2015-07-11 22:28 ` Thomas Petazzoni
2015-07-22 16:56 ` glscantlen [this message]
2015-07-22 20:00 ` Thomas Petazzoni
2015-07-22 23:34 ` glscantlen
2015-07-23 6:57 ` Thomas Petazzoni
2015-07-23 16:25 ` glscantlen
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=1437584173498-106871.post@n4.nabble.com \
--to=glscantlen@gmail.com \
--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