Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 07-17-2015, 01:39 AM   #1
LQ Newbie
Registered: Jul 2015
Posts: 1

Rep: Reputation: Disabled
Problem building uclibc toolchain with yocto

I'm trying to build a cross compiler toolchain for PowerPC (mpc8544).

I'm able to successfully bitbake the meta-toolchain target for glibc, when I check inside the sysroot directory of the sdk, I find the following directories:

ppce500v2-poky-linux-gnuspe x86_64-pokysdk-linux

The directory ppce500v2-poky-linux-gnuspe, contains root filesystem for target (ppc500v2). The directory x86_64-pokysdk-linux, contains the cross development tools, for my host, particularly gcc (powerpc-poky-linux-gnuspe-gcc)

If I execute:

powerpc-poky-linux-gnuspe-gcc -v

the target is set to: powerpc-poky-linux

which I interpret to mean a powerpc based target with glibc&linux

I want to build a uclibc toolchain:

to this I understand you need to add the following line to my local.conf:

TCLIBC = "uclibc"

After doing so, I am again able successfully build the target meta-toolchain. Again if I look inside the sysroot directory two directories have been created:

ppce500v2-poky-linux-uclibcspe x86_64-pokysdk-linux

ppce500v2-poky-linux-uclibcspe, this time the root filesystem is based on uclibc and this is refelected in the name. x86_64-pokysdk-linux, again a directory to hold the host tools has been created. The gcc tools are located in under directory ./usr/bin/powerpc-poky-linux-gnuspe as before,

If I execute:

powerpc-poky-linux-gnuspe-gcc -v

the target is set to: powerpc-poky-linux

However given that I've selected uclibc, I was expecting the gcc tools to be located under a directory: ./usr/bin/powerpc-poky-linux-uclibcspe to reflect the fact that the tools are targeting uclibc.

If I look inside the environment script created by the meta-toolchain target it shares this expectation as is reflected by the extract for CC envvar:

export CC="powerpc-poky-linux-uclibcspe-gcc -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double --sysroot=$SDKTARGETSYSROOT"

If I search the files created by the target meta-toolchain, it has actually created an apprpriate gcc located deeply nested under the work diretcory, a gcc toolset of the correct form has been created, namely:


Just to confirm when I run with the -v option it shows its target as:


Can someone clarify what's happening here?!?

Are my expectations correct?
If so, why is the correct toolchain created, but not put in the correct place by the populate-sdk target?
Thanks in advance for any help you can provide!


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Please help building a toolchain delta67 Linux - General 8 12-02-2014 10:25 AM
Building ARM toolchain mr.simo Linux - Software 2 07-25-2014 06:38 AM
Gentoo Hardened uClibc toolchain z9721 Gentoo 1 02-22-2014 09:32 PM
Problem building the PSP Toolchain under Ubuntu (gcc problem) L-28C Linux - Software 2 09-23-2008 02:38 AM
bulding a gcc toolchain with uclibc behmjose Programming 1 02-29-2004 09:54 PM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 10:43 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration