Hi,
I'm trying to build Open Embedded, which requires running bitbake.
When I do
sudo bitbake console-image
I get the message
ERROR: Please set the 'CACHE' variable.
and it stops.
Anyone know why this should be? I read in another post that bitbake
has a problem with the environment variables, and env variables
should be replaced by hard paths in bitbake.conf, which may be
something to do with it.
I'm building in Ubuntu 8.04 following the directions on
Hi,
I’m trying to build Open Embedded, which requires running bitbake.
When I do
sudo bitbake console-image
I get the message
ERROR: Please set the ‘CACHE’ variable.
and it stops.
Anyone know why this should be? I read in another post that bitbake
has a problem with the environment variables, and env variables
should be replaced by hard paths in bitbake.conf, which may be
something to do with it.
I’m building in Ubuntu 8.04 following the directions on
No you’re not, otherwise you wouldn’t be using ‘sudo bitbake’!!! Now go back and read
Thanks for this advice, Koen. I've managed to get it to run bitbake
now, but it seems to take a long time.
Initially it comes up with
NOTE: Running task 1 of 2946 (ID: 20, /home/peter/OE/openembedded/
recipes/shasum/shasum-native.bb, do_setscene)
and after several hours it's got to task 121 or so.
I'm running it on an old PC with 320M of RAM, is that not up to the
job?
that's exactly what's happening. i have a 64-bit AMD laptop with 4G
of RAM and bitbaking some of the images take hours. your system would
appear to be *woefully* underpowered.
Yes I agree, you have an underpowered system. A very underpowered system. Like Mr. Day, I have a laptop with an Intel dual core processor, 64 bit Fedora 12, and 4 Gb memory. A bitbake of 'base-image' can take 6-8 hours for me. In fact I've read posts on the Gumstix list about people with quad core desktops and more memory doing it much faster...in 30 minutes or so. But these folks probably configured their desktops with fast builds in mind because time is money.