Re: BeagleBone...bitbake -v core-image-sato stops

[kaffeesurrogat@posteo.de]

Hello again,

i've had a closer look to my gentoo system. Since it is an old but 
regularly updated system i am stuck with a non-multilib enabled profile. 
Luckily I have a newer installation on a different machine available and 
until now things compile fine. The new installation is using a 
multilib-enabled profile.
For everything else I've followed the steps mentioned in the yocto wiki 
found on wiki.gentoo.org:

https://wiki.gentoo.org/wiki/Yocto

Have fun,

kaffeesurrogat


Am 06.12.2015 um 18:32 schrieb kaffeesurrogat@posteo.de:
> Thanks so far. I wasn't aware of the log files in temp/log.do_compile 
> directory ;-) Well I've found an error, perhaps not related to 
> attr-native but to gcc:
>
> the log-file says:
>
> + cd 
> /home/nico/yocto_bb/poky/build_bbb/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/gcc-cross-initial/4.8.2-r0/gcc-4.8.2/build.i686-linux.arm-poky-linux-gnueabi
> + do_compile
> + oe_runmake all-gcc all-target-libgcc
> + oe_runmake_call all-gcc all-target-libgcc
> + bbnote make -j 8 'ARCH_FLAGS_FOR_TARGET= -march=armv7-a 
> -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 
> -isystem/home/nico/yocto_bb/poky/build_bbb/tmp/sysroots/beaglebone/usr/include' 
> all-gcc all-target-libgcc
> + echo 'NOTE: make -j 8 ARCH_FLAGS_FOR_TARGET= -march=armv7-a 
> -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 
> -isystem/home/nico/yocto_bb/poky/build_bbb/tmp/sysroots/beaglebone/usr/include 
> all-gcc all-target-libgcc'
> NOTE: make -j 8 ARCH_FLAGS_FOR_TARGET= -march=armv7-a 
> -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 
> -isystem/home/nico/yocto_bb/poky/build_bbb/tmp/sysroots/beaglebone/usr/include 
> all-gcc all-target-libgcc
> + make -j 8 'ARCH_FLAGS_FOR_TARGET= -march=armv7-a -mthumb-interwork 
> -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 
> -isystem/home/nico/yocto_bb/poky/build_bbb/tmp/sysroots/beaglebone/usr/include' 
> all-gcc all-target-libgcc
> make: *** No rule to make target 'all-gcc'.  Stop.
> + die 'oe_runmake failed'
> + bbfatal 'oe_runmake failed'
> + echo 'ERROR: oe_runmake failed'
> ERROR: oe_runmake failed
>
>
> It might happen to be the problem, but I don't know ..... I will poke 
> around, to find some information about setting up the gcc-toolchain. 
> Could this be the problem ?
>
>
> Thanks,
>
> kaffeesurrogat
>
> Am 06.12.2015 um 15:57 schrieb Michael Habibi:
>> You may be able to look under ${WORKDIR}/temp/log.do_compile to see 
>> what the logs are saying it got stuck doing.
>>
>> On Sun, Dec 6, 2015 at 4:16 AM, <kaffeesurrogat@posteo.de 
>> <mailto:kaffeesurrogat@posteo.de>> wrote:
>>
>>     Hello to all,
>>
>>     this is my first question ;-) I'm doing my first steps with a
>>     beaglebone black and yocto. I've bought the beaglebone book "Using
>>     Yocto Project with Beaglebone Black" and started the bitbake with
>>     "bitbake -v core-image-sato". After a while the bitbake-process
>>     reached a package called attr-native-2.4.47-r0 and it was not able
>>     to move on. Bitmaker did not complain about anything, but I've
>>     started the process yesterday in the morning and until now there
>>     was no progress.
>>
>>     I've downloaded the source with:
>>
>>     git clone -b daisy git://git.yoctoproject.org/poky.git
>>     <http://git.yoctoproject.org/poky.git>
>>
>>     My Distro is:
>>
>>     gentoo
>>
>>     I've started the bitbake with:
>>
>>     bitbake -v core-image-sato
>>
>>
>>     Now I'm wondering, if I did something wrong .....
>>
>>     Greetings,
>>
>>     kaffeesurrogat
>>
>>
>>     --
>>     _______________________________________________
>>     yocto mailing list
>>     yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>>     https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>