Bitbake Scripts...

[ironstorm]

June 3, 2005...

My rough work towards making a bitbake image on Debian under QEMU...  There is a problem with the compiler path I can't resolve (says it can't find arm-linux-gcc-2.95, but it is in the path)...

I use a build account called "bitbake" w/ sudo permissions to do everything root can.
I put all of my OE "/stuff" in ~/bb

- unzip this file
- grant sudo privledges to your build account
- cut and paste lines from bitbake_install.txt to command prompt
- get path settings from .bashrc add them to your shell, log out and back in, then type "export" to check your paths for PATH and BBPATH
- run refresh_toolchain.sh to get the latest build of bitbake and OE package data

If you are using a collie (5500), you can copy local.conf to ~/bb/build/conf/local.conf, otherwise you'll have to edit ~/bb/build/conf/local.conf as per the docs @ http://oe.handhelds.org/cgi-bin/moin.cgi/GettingStarted

Once your local.conf is done, you can start a build by doing:
cd ~/bb/build
bitbake openzaurus-sa


Let me know how it works/doesn't for you...

Cheers,
-Ironstorm

[jamesm]

I'll try it out tonight and post the results here.

[lardman]

There is a problem with the compiler path I can't resolve (says it can't find arm-linux-gcc-2.95, but it is in the path)...

Are you sure that you remembered to rename the arm-linux-gcc file to arm-linux-gcc-2.95 ?


Si

[ironstorm]

There is a problem with the compiler path I can't resolve (says it can't find arm-linux-gcc-2.95, but it is in the path)...

Are you sure that you remembered to rename the arm-linux-gcc file to arm-linux-gcc-2.95 ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82641\"][{POST_SNAPBACK}][/a][/div]

Yes, it's gets mv'd in the bitbake_install.txt commands...  And /usr/local/arm/2.95.3/bin
is exported both BBPATH and PATH...

At first I had it symlinked but then I realized that might not work from ZaurusKernels where Mickeyl said that ln might leave it still in the path (it could conflict w/ 3.3 or 3.4 or whatever is used to compile the non-kernel packages, I guess)...

I'm wondering if maybe the directory path is too long or something (the kernel compile like 6 directories below /home/bitbake/bb/build vs. /stuff/build which is used in the OE docs)...

It also seems to work executing the "ccache arm-linux-gcc-2.95 ..." command from the command line in the directory it supposedly died in...

-Ironstorm