[yocto] Build failures on yocto

[Hector Oron]

Hello,

2010/11/1 Richard Purdie <rpurdie at linux.intel.com>:

> I don't have answers to all of the failures but let me try and respond
> to the ones I have some ideas about:


> On Mon, 2010-11-01 at 18:23 +0000, Hector Oron wrote:
>>   lenny_i386)
>> cat <<EOF
>> [...]
>> | NOTE: Running
>> /srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/gmp-native-4.2.4-r0/gmp-4.2.4/configure
>>                 --build=x86_64-linux          --host=x86_64-linux
>>    --target=x86_64-linux
>> --prefix=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr
>>           --exec_prefix=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr
>>
>> --bindir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/bin
>>          --sbindir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/sbin
>>
>> --libexecdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/libexec
>>
>> --datadir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share
>>             --sysconfdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/etc
>>       --sharedstatedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/com
>>              --localstatedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/var
>>         --libdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/lib
>>
>> --includedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/include
>>
>> --oldincludedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/include
>>              --infodir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share/info
>>          --mandir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share/man
>>                                        ...
>> | checking build system type... x86_64-pc-linux-gnu
>> | checking host system type... x86_64-pc-linux-gnu
>> | checking for a BSD-compatible install... /usr/bin/install -c
>> [...]
>> | checking size of unsigned short... 2
>> | checking for unsigned... yes
>> | checking size of unsigned... 4
>> | checking for unsigned long... yes
>> | checking size of unsigned long... 4
>> | checking for mp_limb_t... yes
>> | checking size of mp_limb_t... 4
>> | configure: error: Oops, mp_limb_t is 32 bits, but the assembler code
>> | in this configuration expects 64 bits.
>> | You appear to have set $CFLAGS, perhaps you also need to tell GMP the
>> | intended ABI, see "ABI and ISA" in the manual.
>> | FATAL: oe_runconf failed
>> NOTE: Task failed:
>> /srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/gmp-native-4.2.4-r0/temp/log.do_configure.28892
>> NOTE: package gmp-native-4.2.4-r0: task do_configure: failed
>> ERROR: TaskFailed event exception, aborting
>> NOTE: package gmp-native-4.2.4: failed
>> ERROR: Build of
>> /srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb
>> do_configure failed
>> ERROR: Task 556
>> (/srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb,
>> do_configure) failed
>> NOTE: Tasks Summary: Attempted 135 tasks of which 135 didn't need to
>> be rerun and 1 failed.
>> ERROR: '/srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb'
>> failed
>> NOTE: build 201011011717: completed
>> make: *** [/srv/build/builds/menuconfig2-i386/../build/rootfs/yocto/purple-3.2/foo]
>> Error 1
>> EOF
>
> At a guess this is a 64 bit kernel and a 32 bit userspace? What does
> "uname -a" show?

Yes, it is 64 bit kernel host running a 32 bit userland.
Linux enorme 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

> I suspect if you add
>
> BUILD_ARCH = "i686"
>
> to your local.conf, the build might work better? If you can confirm that
> we can probably detect this problem and avoid this failure.

Build attempted with
BUILD_ARCH="i686" BB_NUMBER_THREADS="2" PARALLEL_MAKE="-j 2"
MACHINE=$(BOARD) bitbake $(YOCTO_IMAGE)
got same result as above.

> Same as the above failure (64 bit kernel and 32 bit userspace)?

Sure.

>>   others|*)
>> cat <<EOF
>>     - I need to setup "vm.mmap_min_addr = 0" under /etc/sysctl.conf
>
> Right, but it detected that?

If it was not set, scripts warn about it, once you set it up, it goes through.

Best regards,
-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."

-- Day DVB-T stop working nicely
Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html