All of lore.kernel.org
 help / color / mirror / Atom feed
From: kaffeesurrogat@posteo.de
To: yocto@yoctoproject.org
Subject: Re: BeagleBone...bitbake -v core-image-sato stops
Date: Sun, 6 Dec 2015 18:32:59 +0100	[thread overview]
Message-ID: <5664714B.1040909@posteo.de> (raw)
In-Reply-To: <CAOsp8o_+Tf4n2a7_TzScRK1=b56F6=ikknXgrrwt4T8CEJYUrg@mail.gmail.com>

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
>
>



  reply	other threads:[~2015-12-06 17:33 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 [this message]
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
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=5664714B.1040909@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.