[yocto] [SOLVED] Re: BeagleBone...bitbake -v core-image-sato stops
kaffeesurrogat
kaffeesurrogat at posteo.de
Sun Jan 3 03:24:34 PST 2016
Hello to all and a happy new year,
the do_compile of attr-native is finishing now on a gentoo host.
I've copied the source of attr-native over to my gentoo host and run the
./configure, make .... process.
I've compared the config.log - files of yocto and gentoo. The difference
was " enable_gettext='yes' " on the gentoo host
and " enable_gettext='no' " in the yocto-build-environment. Disabling
gettext on the gentoo host led to the same behaviour. The compilation or
linking stopped wiht the message "o fr.mo fr.po".
I've changed the variable EXTRA_OECONF.... to:
EXTRA_OECONF_append_class-native = " --enable-gettext=yes" in the file
"ea-acl.inc" of the yocto-project, which resides in
"meta/recipes-support/attr/". The build finished.
As Khem Raj told me, I've used a virtualmachine with ubuntu to build the
yocto-project. On ubuntu there was no need to enable gettext via
ea-acl.inc. The build finished without any extra measures.
Have fun,
kaffessurrogat
On 29.12.2015 11:21, kaffeesurrogat wrote:
>
> On 28.12.2015 23:00, Khem Raj wrote:
>>> On Dec 28, 2015, at 8:56 AM, kaffeesurrogat
>>> <kaffeesurrogat at posteo.de> wrote:
>>>
>>> Hello again,
>>>
>>> well I'm really a noob and guessing what to do. Well I've
>>> interrupted bitbake cause
>>> nothing was happing and the log.do_compile of attr-native didn't
>>> show any error message. I've started it all over again an now I do
>>> get an error message: yes ;-)
>>>
>>> it says:
>>>
>>> gmake[2]: ../-libtool: Command not found
>>>
>>> This looks a little bit weird to me, especially the "minus" in front
>>> of the "libtool" .....
>>>
>>> Where does it come from? A missing or empty variable? Something like
>>> ${MYNAMEIS}-libtool an ${MYNAMEIS} not known?
>>>
>> what is your build host ?.
>> I would suggest to setup a clean build system ( may be a VM ) and try
>> it out on that
>
> Thanks Khem Raj,
>
> my build host is a gentoo system. I know it is not officially
> supported, but I'm using it for ages. Thus I know my way around. At
> least a little bit. Would be nice not to switch.
> I've removed my yocto-dir several times and made a fresh git-clone.
> I've tried with the daisy and the jethro branch. I've tried to build
> core-image-minimal and core-image-sato for qemu and the beaglebone
> black. I did that on two different gentoo-machines, on one of them
> things compiled fine. In the beginning I've had the impression, the
> faults on the failing-gentoo system could be due to the missing
> multilib support. Thus I replaced it with a fresh and clean install
> supporting gcc-multilib stuff.
>
> The error stays - with small variation - more or less the same:
>
> attr-native does not finish its build-process.
>
> 1) It stops with the message similiar to "o pl.mo pl.poto" after gmake
> left the directory getfattr or setfattr
>
> or
>
> 2) It fails with "gmake[2]: o: Command not found"
>
> or
>
> 3) It fails with "gmake[2]: ../-libtool: Command not found "
>
>
> This is really weird. I'm not able to figure the small but important
> differences on my two different gentoo machines.
>
> Any help is really appreciated,
>
> Kaffesurrogat
>
>>>>> Sorry guys .....
>>>>>
>>>>> I thought I was done. Actually I'm not a bit smarter then before ;-)
>>>>>
>>>>> I'm still trying to build a yocto-image for a beaglebone. I
>>>>> believed, that the reason why yocto stopped compiling at
>>>>> attr-native-2.4.47-r0 was the missing gcc-multilib support. I've
>>>>> tried the same build on a gentoo machine at work, which had a
>>>>> multilib environment, and it finished.
>>>>>
>>>>> I've setup a new gentoo with multilib environment on my laptop but
>>>>> ...... bitbake stops again at attr-native. So this was not the
>>>>> trick. The log.do_compile in
>>>>>
>>>>> /home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/work/x86_64-linux/attr-native/2.4.47-r0/temp
>>>>>
>>>>>
>>>>> says nothing special, at least for me. Here is the quote:
>>>>>
>>>>> -----------------------------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> x86_64-linux-libtool: link: gcc -o .libs/setfattr -Wl,-rpath-link
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/usr/lib
>>>>> -Wl,-rpath-link
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/lib
>>>>> -Wl,-rpath
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/usr/lib
>>>>> -Wl,-rpath
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/lib
>>>>> -Wl,-O1 -Wl,-rpath-link
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/usr/lib
>>>>> -Wl,-rpath-link
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/lib
>>>>> -Wl,-rpath
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/usr/lib
>>>>> -Wl,-rpath
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/lib
>>>>> -Wl,-O1 -Wl,-rpath-link
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/usr/lib
>>>>> -Wl,-rpath-link
>>>>> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/lib
> -Wl,-rpath
> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysroots/x86_64-linux/usr/lib
> -Wl,-rpath
> -Wl,/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/sysrootgmake[2]:
> Leaving directory
> '/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/work/x86_64-linux/attr-native/2.4.47-r0/attr-2.4.47/setfattr'
>>>>>
>>>>> o fr.mo fr.po
>>>>>
>>>>> -------------------------------------------------------------------------------------------------------
>>>>>
>>>>
>>>> ADD-ON:
>>>>
>>>> I've had a look in the log.do-compile-file on my machine at work. It
>>>> says .....
>>>>
>>>> -----------------------------------------------------------------------------------------------------------
>>>>
>>>>
>>>> o fr.mo fr.po
>>>> gmake[3]: Nothing to be done for 'default'.
>>>> gmake[3]: Leaving directory
>>>> '/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/work/x86_64-linux/attr-native/2.4.47-r0/attr-2.4.47/man/man1'
>>>>
>>>> /usr/bin/gmake -C man2
>>>> gmake[2]: o: Command not found
>>>> ../include/buildrules:66: recipe for target 'fr.mo' failed
>>>> gmake[2]: [fr.mo] Error 127 (ignored)
>>>>
>>>> -----------------------------------------------------------------------------------------------------------
>>>>
>>>>
>>>> Well ..... ????????????????
>>>>
>>>>> It will stay at this point forever.
>>>>>
>>>>>
>>>>> The last output messages of bitbake:
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> + rm -rf
>>>>> /home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/3.14.4+gitAUTOINC+183622e809_0143c6ebb4-r0/sstate-build-populate_lic/
>>>>>
>>>>> + ret=0
>>>>> + trap '' 0
>>>>> + exit 0
>>>>>
>>>>> [INFO] Pre-processed cfg file beaglebone-standard-config-3.14.4
>>>>> created.
>>>>> [INFO] processing of raw cfg data completed.
>>>>>
>>>>>
>>>>> ********************************************************************************
>>>>>
>>>>> Configuration stored in
>>>>> /home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/3.14.4+gitAUTOINC+183622e809_0143c6ebb4-r0/linux-beaglebone-standard-build/.config
>>>>> ********************************************************************************
>>>>>
>>>>>
>>>>> To build with this kernel configuration, ensure a suitable
>>>>> toolchain
>>>>> is in your path for arm, note its common command prefix, and do:
>>>>>
>>>>> make
>>>>> O=/home/nico/yocto_bbb_daisy/poky/build_bbb/tmp/work/beaglebone-poky-linux-gnueabi/linux-yocto/3.14.4+gitAUTOINC+183622e809_0143c6ebb4-r0/linux-beaglebone-standard-build
>>>>> ARCH=arm \
>>>>> CROSS_COMPILE=<cross-compile-prefix>
>>>>>
>>>>>
>>>>> + '[' 0 -ne 0 ']'
>>>>>
>>>>> + echo '# Global settings from linux recipe'
>>>>> + echo 'CONFIG_LOCALVERSION="-yocto-standard"'
>>>>> + ret=0
>>>>> + trap '' 0
>>>>> + exit 0
>>>>>
>>>>> Currently 1 running tasks (1040 of 1770):
>>>>> 0: attr-native-2.4.47-r0 do_compile (pid 1778)
>>>>>
>>>>> -------------------------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> To be honest, I'm lost ....
>>>>>
>>>>> Would be happy about some help,
>>>>>
>>>>> kaffeesurrogat
>>>>>
>>>>>
>>>>> On 07.12.2015 21:16, kaffeesurrogat at posteo.de wrote:
>>>>>> 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
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto at yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>
>
More information about the yocto
mailing list