From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ChenQi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Failure
Date: Mon, 02 Sep 2013 10:57:11 +0100 [thread overview]
Message-ID: <1378115831.1059.169.camel@ted> (raw)
In-Reply-To: <5223FB7E.6070306@windriver.com>
On Mon, 2013-09-02 at 10:44 +0800, ChenQi wrote:
> On 09/02/2013 10:08 AM, Otavio Salvador wrote:
> > Hello,
> >
> > I got this build failure today; I am about to leave so I removed the
> > tmpdir and will let it running during night. I post more info if/when
> > I reproduce it again:
> >
> > Patch redhat-portability.diff does not apply (enforce with -f)
> > ERROR: Function failed: patch_do_patch
> > ERROR: Logfile of failure stored in:
> > /home/otavio/hacking/freescale/fsl-community-bsp-mx6/build/tmp/work/x86_64-linux/elfutils-native/0.155-r0/temp/log.do_patch.20173
> > ERROR: Task 662
> > (virtual:native:/home/otavio/hacking/freescale/fsl-community-bsp-mx6/sources/poky/meta/recipes-devtools/elfutils/elfutils_0.155.bb,
> > do_patch) failed with exit code '1'
> >
> > Regards,
> >
>
> I got the same error now and then when building native-elfutils. Every
> time the error appears, I have to clean the sstate cache for elfutils.
No, you don't, you need to *clean* elfutils, sstate is just fine.
I suspect the issue is that there is some patch to the source code and
then further modifications happen at do_configure/do_compile time. If we
try and rerun do_patch (due to the patch.bbclass change recently), it
can no longer unapply the patch and things fail.
Cheers,
Richard
next prev parent reply other threads:[~2013-09-02 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 2:08 Failure Otavio Salvador
2013-09-02 2:44 ` Failure ChenQi
2013-09-02 9:57 ` Richard Purdie [this message]
2013-09-02 10:25 ` Failure Richard Purdie
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=1378115831.1059.169.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.com \
--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