[Buildroot] build libstdc++.so.6

[Buildroot] build libstdc++.so.6

[glscantlen]

I am using external custom toolchain Linaro-4.9
Linaro has been downloaded from the binary archive,
gcc-linaro-4.9-2015.02-3-x86_64_arm-linux-gnueabihf
How/Can BuildRoot build the libstdc++.so.6 library ?

Gary



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/build-libstdc-so-6-tp105322.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] build libstdc++.so.6

[Thomas Petazzoni]

Hello,

On Sat, 11 Jul 2015 10:03:50 -0700 (PDT), glscantlen wrote:
> I am using external custom toolchain Linaro-4.9
> Linaro has been downloaded from the binary archive,
> gcc-linaro-4.9-2015.02-3-x86_64_arm-linux-gnueabihf
> How/Can BuildRoot build the libstdc++.so.6 library ?

If you're using an external toolchain, then the libstdc++.so.6 library
is provided by the external toolchain.

However, we have not yet looked at the 2015.02 Linaro toolchain. Unless
you specifically need this toolchain, I would recommend you to use the
pre-configured Linaro toolchain available in Buildroot.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] build libstdc++.so.6

[glscantlen]

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.

[Buildroot] build libstdc++.so.6

[Thomas Petazzoni]

Hello,

On Wed, 22 Jul 2015 09:56:13 -0700 (PDT), glscantlen wrote:

> 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.

Just use the Linaro 14.09 toolchain that is pre-defined in Buildroot.
Buildroot will automatically download it, extract it and set it up for
you. I.e nothing to do or worry about.

> 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/

Which HW platform are you working with? We already have some packages
for the Mali GPU drivers for some platforms. And we could add more.

Basically, it seems to me that you are trying to hack very complicated
things while there are much simpler and better solutions that exist and
that you don't know about.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] build libstdc++.so.6

[glscantlen]

Thanks Thomas,

I'll sure try Linaro 14.09 toolchain.
As long as I can make clean without having to rebuild.

I am using the Odroid-XU3, Samsung 5422 SOC.
I use the kernel and u-boot from the hardkernel repository.
I then added the X11 armsoc driver into the buildroot build.

>Basically, it seems to me that you are trying to hack very complicated 
>things while there are much simpler and better solutions that exist and 
>that you don't know about. 

No doubt about that !
If you don't mind I would appreciate any assistance.
I have a github where I am trying to assemble instructions for others
to see what I've done. goto:
https://github.com/glscantlen/instructions/blob/master/README
https://github.com/glscantlen/instructions/blob/master/Buildroot_XU3_MPlayer/build_xu3_mplayer.ins

Gary







--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/build-libstdc-so-6-with-custom-toolchain-Linaro-4-9-tp105322p106967.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] build libstdc++.so.6

[Thomas Petazzoni]

Hello,

On Wed, 22 Jul 2015 16:34:47 -0700 (PDT), glscantlen wrote:

> No doubt about that !
> If you don't mind I would appreciate any assistance.
> I have a github where I am trying to assemble instructions for others
> to see what I've done. goto:
> https://github.com/glscantlen/instructions/blob/master/README
> https://github.com/glscantlen/instructions/blob/master/Buildroot_XU3_MPlayer/build_xu3_mplayer.ins

As I suspected, this is *really* much more complicated than it needs to
be, and some of the steps are clearly violating the best practices of
Buildroot usage.

Some comments:

 1/ Don't download the Linaro toolchain manually, let Buildroot do it.

 2/ Don't download/build U-Boot manually, let Buildroot do it

 3/ You can try to use the genimage tool to generate the complete
    filesystem image rather than doing all those manual dd commands and
    fiddling with partprobe and al. See board/wandboard/genimage.cfg
    for an example in Buildroot. In the end, your instructions should
    be as simple as board/wandboard/readme.txt.

 4/ Don't manually explain the addition of your X.org armsoc driver
    package. Put your Buildroot Git tree somewhere, and use it.
    Manually describing changes is completely unreliable and
    inefficient. Also, please submit this package for integration in
    the upstream Buildroot.

 5/ Don't add anything to system/skeleton/, this is completely *ugly*.
    For youtube-dl, create a Buildroot package. For other changes, use
    a rootfs overlay (see the Buildroot manual for details). To
    adjust /etc/network/interfaces for DHCP on eth0, just set the
    option BR2_SYSTEM_DHCP.

 6/ Don't download/build the Linux kernel manually, let Buildroot do
    it.

 7/ Don't put a view of what needs to be enabled in menuconfig, just
    ship a defconfig for your configuration.

 8/ Don't manually fiddle with the Mali driver, create a Buildroot
    package for it.

All in all, if your documentation is not just:

	make <foobar>_defconfig
	make
	<some simple instructions to transfer the image to the SD card or using fastboot>

Then you got something wrong.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] build libstdc++.so.6

[glscantlen]

Thanks for these suggestions. It's all good and useful. Too much to address
all at once. I will attack them one at a time and try to keep this thread
updated with my progress. I agree with your summary and the final build
process should be as clean and simple as possible. That is my goal too.

For the "instructions" my intent was to show the reader how I arrived at the
"simple clean build process". It is more of an instruction on how to create
the build not just instructions on how to execute the build. So for
addressing points like #7, I would keep these instructions. They are
procedures for creating "odroidxu3_mplayer_defconfig". You could argue there
are better ways to present the procedures but that may be of some personal
preference.

Thanks again for your expertise and assistance.
If you prefer that I start a new thread or continue this discussion
else-where I can accommodate.




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/build-libstdc-so-6-with-custom-toolchain-Linaro-4-9-tp105322p107004.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.