All of lore.kernel.org
 help / color / mirror / Atom feed
From: kaffeesurrogat <kaffeesurrogat@posteo.de>
To: yocto@yoctoproject.org
Subject: Re: BeagleBone...bitbake -v core-image-sato stops
Date: Mon, 28 Dec 2015 10:58:46 +0100	[thread overview]
Message-ID: <568107D6.5080406@posteo.de> (raw)
In-Reply-To: <5680F9A5.7040602@posteo.de>

Sorry for sending the same mail twice. I've mixed up my identities.


On 28.12.2015 09:58, kaffeesurrogat@posteo.de 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/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@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
>



  parent reply	other threads:[~2015-12-28  9:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 10:16 BeagleBone...bitbake -v core-image-sato stops kaffeesurrogat
2015-12-06 14:57 ` Michael Habibi
2015-12-06 17:32   ` kaffeesurrogat
2015-12-07 20:16     ` kaffeesurrogat
2015-12-28  8:58       ` kaffeesurrogat
2015-12-28  9:09         ` Nico Mock
2015-12-28  9:31           ` kaffeesurrogat
2015-12-28  9:58         ` kaffeesurrogat [this message]
2015-12-28 16:56           ` kaffeesurrogat
2015-12-28 22:00             ` Khem Raj
2015-12-29 10:21               ` kaffeesurrogat
2016-01-03 11:24                 ` [SOLVED] " kaffeesurrogat
2016-01-03 16:27                   ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=568107D6.5080406@posteo.de \
    --to=kaffeesurrogat@posteo.de \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.