BeagleBone...bitbake -v core-image-sato stops
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
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
You may be able to look under ${WORKDIR}/temp/log.do_compile to see what the logs are saying it got stuck doing.
Quoted 37 lines · On Sun, Dec 6, 2015 at 4:16 AM, <[email protected]> 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.gitMy 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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
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:
Quoted 43 lines
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, <[email protected] <mailto:[email protected]>> 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
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto
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 [email protected]:
Quoted 84 lines
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_runmakeall-gcc all-target-libgcc
+oe_runmake_callall-gcc all-target-libgcc
+ bbnote make -j 8 'ARCH_FLAGS_FOR_TARGET= -march=armv7-a(quoted diff) +0
-2-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(quoted diff) +0
-2-mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 -isystem/home/nico/yocto_bb/poky/build_bbb/tmp/sysroots/beaglebone/usr/includeall-gcc all-target-libgcc'
NOTE: make -j 8 ARCH_FLAGS_FOR_TARGET= -march=armv7-a(quoted diff) +0
-2-mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a8 -isystem/home/nico/yocto_bb/poky/build_bbb/tmp/sysroots/beaglebone/usr/includeall-gcc all-target-libgcc
+ make -j 8 'ARCH_FLAGS_FOR_TARGET= -march=armv7-a -mthumb-interwork(quoted diff) +0
-2-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_runmakefailed'
+ bbfatal 'oe_runmakefailed'
+ echo 'ERROR:oe_runmakefailed'
ERROR:oe_runmakefailedIt 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:
Quoted 43 lines
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, <[email protected] <mailto:[email protected]>> 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
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto
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
-------------------------------------------------------------------------------------------------------
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
Quoted 1 line · On 07.12.2015 21:16, [email protected] 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
Quoted 42 lines · On 28.12.2015 09:58, [email protected] wrote:
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/tempsays nothing special, at least for me. Here is the quote:
-----------------------------------------------------------------------------------------------------
x86_64-linux-libtool: link: gcc -o .libs/setfattr -Wl,-rpath-link
(quoted diff) +0
-23-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'
Quoted 5 lines
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 ..... ????????????????
Quoted 59 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 1 line · On 07.12.2015 21:16, [email protected] 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
-------- Forwarded Message --------
Subject: Re: [yocto] BeagleBone...bitbake -v core-image-sato stops
Date: Mon, 28 Dec 2015 10:09:09 +0100
From: Nico Mock <[email protected]>
To: [email protected]
Quoted 49 lines · On 28.12.2015 09:58, [email protected] wrote:
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/tempsays nothing special, at least for me. Here is the quote:
-----------------------------------------------------------------------------------------------------
x86_64-linux-libtool: link: gcc -o .libs/setfattr -Wl,-rpath-link
(quoted diff) +0
-23-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'
Quoted 5 lines
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 ..... ????????????????
Quoted 61 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 2 lines · On 07.12.2015 21:16, [email protected] 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
Sorry for sending the same mail twice. I've mixed up my identities.
Quoted 42 lines · On 28.12.2015 09:58, [email protected] wrote:
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/tempsays nothing special, at least for me. Here is the quote:
-----------------------------------------------------------------------------------------------------
x86_64-linux-libtool: link: gcc -o .libs/setfattr -Wl,-rpath-link
(quoted diff) +0
-23-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'
Quoted 4 lines
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 ..... ????????????????
Quoted 60 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 1 line · On 07.12.2015 21:16, [email protected] 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
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?
Greetings,
Kaffeesurrogat
Quoted 136 lines · kaffeesurrogat
Sorry for sending the same mail twice. I've mixed up my identities.
Quoted 42 lines · On 28.12.2015 09:58, [email protected] wrote:
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/tempsays nothing special, at least for me. Here is the quote:
-----------------------------------------------------------------------------------------------------
x86_64-linux-libtool: link: gcc -o .libs/setfattr -Wl,-rpath-link
(quoted diff) +0
-23-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'Quoted 4 lines
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 ..... ????????????????
Quoted 60 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 1 line · On 07.12.2015 21:16, [email protected] 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
Quoted 8 lines · kaffeesurrogat
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 ;-)
Quoted 8 lines
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
Quoted 111 lines
Greetings,
Kaffeesurrogat
Quoted 41 lines · kaffeesurrogat
Sorry for sending the same mail twice. I've mixed up my identities.
Quoted 12 lines · On 28.12.2015 09:58, [email protected] wrote:
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/tempsays nothing special, at least for me. Here is the quote:
Quoted 7 lines
-----------------------------------------------------------------------------------------------------
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)Quoted 58 lines
-----------------------------------------------------------------------------------------------------------
Well ..... ????????????????
Quoted 53 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 1 line · On 07.12.2015 21:16, [email protected] 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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 9 lines · Khem Raj
Quoted 9 lines · kaffeesurrogat
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:
Quoted 8 lines
Quoted 6 lines
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
Quoted 96 lines
Quoted 96 lines
Quoted 36 lines
Quoted 12 lines
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/tempsays nothing special, at least for me. Here is the quote:
Quoted 7 lines
-----------------------------------------------------------------------------------------------------
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)Quoted 55 lines
-----------------------------------------------------------------------------------------------------------
Well ..... ????????????????
Quoted 51 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 1 line · On 07.12.2015 21:16, [email protected] 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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
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
Quoted 182 lines · kaffeesurrogat
Quoted 9 lines · Khem Raj
Quoted 9 lines · kaffeesurrogat
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:
Quoted 8 lines
Quoted 6 lines
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 thatThanks 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
Quoted 28 lines
Quoted 28 lines
Quoted 28 lines
Quoted 28 lines
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/tempsays nothing special, at least for me. Here is the quote:
-----------------------------------------------------------------------------------------------------
x86_64-linux-libtool: link: gcc -o .libs/setfattr -Wl,-rpath-link
(quoted diff) +0
-11-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/libQuoted 8 lines
Quoted 8 lines
Quoted 8 lines
Review
Quoted 8 lines
(quoted diff) +0
-8-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
(quoted diff) +0
-3-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'Quoted 93 lines
Quoted 93 lines
Quoted 88 lines
Quoted 5 lines
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 ..... ????????????????
Quoted 59 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 1 line · On 07.12.2015 21:16, [email protected] 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-gnueabiSignature · 4 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Quoted 13 lines · kaffeesurrogat
Hello to all and a happy new year,
the
do_compileof 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".
Quoted 8 lines
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.
you should see why it worked on ubuntu. why gettext is not detected on gentoo. native packages should not disable it
Quoted 230 lines
Have fun,
kaffessurrogat
Quoted 112 lines · kaffeesurrogat
Quoted 19 lines · Khem Raj
Quoted 19 lines
On Dec 28, 2015, at 8:56 AM, kaffeesurrogat <[email protected]> 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" .....
Quoted 6 lines
Quoted 3 lines
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 thatThanks 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
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
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/tempsays nothing special, at least for me. Here is the quote:
-----------------------------------------------------------------------------------------------------
x86_64-linux-libtool: link: gcc -o .libs/setfattr -Wl,-rpath-link
(quoted diff) +0
-11-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/libQuoted 8 lines
Quoted 8 lines
Quoted 8 lines
Review
Quoted 8 lines
(quoted diff) +0
-8-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
(quoted diff) +0
-3-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]: LeavingQuoted 104 lines
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'Quoted 99 lines
Quoted 99 lines
Quoted 27 lines
Quoted 6 lines
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)Quoted 66 lines
-----------------------------------------------------------------------------------------------------------
Well ..... ????????????????
Quoted 62 lines
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 0Currently 1 running tasks (1040 of 1770):
0: attr-native-2.4.47-r0do_compile(pid 1778)-------------------------------------------------------------------------------------------------
To be honest, I'm lost ....
Would be happy about some help,
kaffeesurrogat
Quoted 3 lines · On 07.12.2015 21:16, [email protected] 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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto