Re: psuedo-native strangeness on 64 bit build machine

["Petr Štetiar" <ynezz@true.cz>]

Mark Hatle <mark.hatle@windriver.com> [2012-02-28 23:13:47]:

> On 2/28/12 10:35 PM, Steve Sakoman wrote:
>> I did a clean build on an Ubuntu 64 bit build machine a couple of days
>> ago with no issues.

I can confirm same situation here.

>> After a pull of today I did an image build for an OMAP3 machine and
>> encountered an issue with psuedo-native.

Just pseudo? What's your setup, I mean layers etc. Are you using Angstrom's
setup-scripts?

>> Has anyone else been successful building on 64 bit machines?

What version of Ubuntu is that? I'm on 12.04.

> I'm building pseudo on 64-bit machines right now, no problem.

I think, that it's some problem with parallel make. If I clean the stamps and
tmp dir of pseudo-native manually (-c cleanall doesn't work actually, because
pseudo-native is missing, chicken-egg problem? :)) and set PARALLEL_MAKE=1
NUM_THREADS=-j1, then it builds just fine.

There must have been something introduced in the bitbake or the layers
recently, since I was able to build Angstrom/systemd-image/beagleboard from
scratch 3 weeks ago with the same settings (PARALLEL_MAKE=4 NUM_THREADS=-j4").
Now it's impossible to finish the build, the most noticeable failure is gcc,
which fails for me in patching task due to the parallel build settings.
Changing the parallel settings back to 1 helps here also.

-- ynezz