From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Adolfo Sanchez <adolfo_sm_cr@hotmail.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Failing build following Quick Start
Date: Thu, 08 Sep 2016 08:30:58 +0100 [thread overview]
Message-ID: <1473319858.20226.145.camel@linuxfoundation.org> (raw)
In-Reply-To: <SN2PR10MB009442733EA473DB41981EB1CFF90@SN2PR10MB0094.namprd10.prod.outlook.com>
On Tue, 2016-09-06 at 13:13 +0000, Adolfo Sanchez wrote:
> I am new to Yocto and trying to learn the basics of the system
>
> I am following the Yocto Quick Start guide:
> http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-q
> s.html
>
> Details:
> 1) I am using Lubuntu 16.04 64bits on a Oracle VirtualBox VM, over a
> Windows10 host.
> 2) I downloaded the poky from the Yocto page instead of download it
> via git
> 3) I am tryting to build the basic core-image-sato for qemu
> 4) I am getting the following error:
> ERROR: Task 1921 (virtual:native:/home/adolfo/Yocto-testin/poky-
> krogoth-15.0.1/meta/recipes-support/gmp/gmp_6.1.0.bb, do_compile)
> failed with exit code '1'
> 5) I test the ${WORKDIR}/temp/run.do_compile I get the following
> error:
> x86_64-linux-libtool: error: 'abs.lo' is not a valid libtool object
> Makefile:421: recipe for target 'libmpq.la' failed
> make[2]: *** [libmpq.la] Error 1
>
> Any help would be appreciated.
Is this error reproducible, e.g. if you run "bitbake gmp-native -c
clean" which will wipe out the piece of source code that is failing,
then run "bitbake core-image-sato" again, does it work?
Cheers,
Richard
prev parent reply other threads:[~2016-09-08 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 13:13 Failing build following Quick Start Adolfo Sanchez
2016-09-06 15:47 ` xerofoify
2016-09-07 2:22 ` Adolfo Sanchez
2016-09-07 2:28 ` Nicholas Krause
2016-09-08 7:30 ` Richard Purdie [this message]
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=1473319858.20226.145.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=adolfo_sm_cr@hotmail.com \
--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.