From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Fathi Boudra <fathi.boudra@linaro.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ltp: update to 20140828 release
Date: Tue, 04 Nov 2014 15:54:58 +0000 [thread overview]
Message-ID: <1415116498.23396.33.camel@ted> (raw)
In-Reply-To: <CAGNsrLAPfA4=UH0GXkPeAmOx-GbJ7pnNF3gDaRixwNhNKw41og@mail.gmail.com>
On Tue, 2014-11-04 at 17:10 +0200, Fathi Boudra wrote:
> after a lot of finger-pointing and implying we don't test our changes
> or do our homework or do clean builds:
> * I've built ltp for armv7a and armv8 on our builders and it works
> fine
> * I've built poky for x86 and it built fine
>
> here's my steps:
> $ git clone git://git.yoctoproject.org/poky
> $ cd poky
> $ source oe-init-build-env
> $ patch -p1 < 0001-ltp-update-to-20140828-release.patch
> $ bitbake ltp
>
> $ ls -l tmp/deploy/rpm/i586/ltp-*
> -rw-r--r-- 2 user user 55929600 Nov 4 16:28
> tmp/deploy/rpm/i586/ltp-20140828-r0.i586.rpm
> -rw-r--r-- 2 user user 3080 Nov 4 16:28
> tmp/deploy/rpm/i586/ltp-dbg-20140828-r0.i586.rpm
> -rw-r--r-- 2 user user 3264 Nov 4 16:28
> tmp/deploy/rpm/i586/ltp-dev-20140828-r0.i586.rpm
> -rw-r--r-- 2 user user 31884 Nov 4 16:28
> tmp/deploy/rpm/i586/ltp-doc-20140828-r0.i586.rpm
>
> afaict, the failure isn't related to the changes submitted. Could you
> be kind enough to try to reproduce the build failure outside of the
> yocto autobuilders? or give me the exact steps to reproduce the
> failure?
bitbake libtirpc; bitbake ltp
seems to reliably reproduce for me.
Cheers,
Richard
next prev parent reply other threads:[~2014-11-04 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 8:38 [PATCH] ltp: update to 20140828 release Fathi Boudra
2014-10-31 9:44 ` Burton, Ross
2014-10-31 10:58 ` Richard Purdie
2014-10-31 12:46 ` Fathi Boudra
2014-10-31 20:09 ` Burton, Ross
2014-11-04 15:10 ` Fathi Boudra
2014-11-04 15:54 ` Richard Purdie [this message]
2014-11-05 10:20 ` Fathi Boudra
2014-11-05 10:33 ` Burton, Ross
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=1415116498.23396.33.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=fathi.boudra@linaro.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox