All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] gcc-cross-initial patching fails
Date: Mon, 27 Feb 2012 12:19:24 +0000	[thread overview]
Message-ID: <1330345164.4593.18.camel@ted> (raw)
In-Reply-To: <CALbNGRQU7BDK5WGYgaXbCwmki922wk_EBkBqZadLL5G=5pCPQA@mail.gmail.com>

On Mon, 2012-02-27 at 12:37 +0100, Andreas Müller wrote:
> On Thu, Feb 23, 2012 at 8:18 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >
> > Op 22 feb. 2012, om 22:39 heeft Andreas Müller het volgende geschreven:
> >
> >> On Wed, Feb 22, 2012 at 10:18 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >>> On Wed, Feb 22, 2012 at 12:15 PM, McClintock Matthew-B29882
> >>> <B29882@freescale.com> wrote:
> >>>>> Applying patch gcc45-no-add-needed.patch
> >>>>> patching file gcc/config/alpha/elf.h
> >>>>> patching file gcc/config/ia64/linux.h
> >>>>> patching file gcc/config/linux.h
> >>>>> Hunk #1 succeeded at 89 (offset -12 lines).
> >>>>> patching file gcc/config/rs6000/sysv4.h
> >>>>> Hunk #1 FAILED at 908.
> >>>>> 1 out of 1 hunk FAILED -- rejects in file gcc/config/rs6000/sysv4.h
> >>>>> Patch gcc45-no-add-needed.patch does not apply (enforce with -f)
> >>>>> ERROR: Function failed: patch_do_patch
> >>>>> ERROR: Logfile of failure stored in:
> >>>>> /home/Superandy/tmp/oe-core-eglibc/work-shared/gcc-4.5-r45+svnr181733/temp/log.do_patch.5367
> >>>>> NOTE: package gcc-cross-initial-4.5-r45+svnr181733: task do_patch: Failed
> >>>>> ERROR: Task 2829
> >>>>> (/home/Superandy/data/oe-core/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-initial_4.5.bb,
> >>>>> do_patch) failed with exit code '1'
> >>>>>
> >>>>> git log does not help me much -  what goes wrong?
> >>>>
> >>>> Which actual patch is it failing on? Is there a conflict between
> >>>> oe-core and meta-oe patch set against gcc?
> >>>
> >>> gcc45-no-add-needed.patch is the patch in question. I dont see
> >>> anything wrong with it.
> >>> Can you do bitbake -ccleanall gcc-cross-initial and redo bitbake
> >>> gcc-cross-initial -cpatch ?
> >>>
> >> FYI: I removed the line which came in by the commits I mentioned above
> >>
> >> should_apply[vardepsexclude] += "PN"
> >>
> >> in openembedded-core/meta/recipes-devtools/gcc/gcc-common.inc
> >>
> >> and build from scratch works without issues.
> >
> > I received reports of the same problem and I handed your fix to them, I'm waiting to hear back.
> >
> Having some experience to this problem now, I have the feeling that
> there is some race condition on patching. I think gcc-cross-initial /
> gcc-cross-intermediate / gcc-runtime share same source directory -
> correct me if I am wrong. In case all start patching about the same
> time, the patches don't match for those being late. This theory is
> encouraged by the fact that the following sequence helps when building
> from scratch:
> 
> 1. bitbake gcc-cross-initial
> 2. bitbake gcc-cross-intermediate
> 3. bitbake gcc-runtime
> 4. bitbake <my-image>

Does gcc-4.5 have different patch sets for any of the above?

Its now being assumed there is one good patch set shared by all the
recipes (since we're sharing the source directory). If that were not the
case it would explain the issues some people are reporting...

Cheers,

Richard




  reply	other threads:[~2012-02-27 12:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 20:13 gcc-cross-initial patching fails Andreas Müller
2012-02-22 20:15 ` McClintock Matthew-B29882
2012-02-22 21:18   ` Khem Raj
2012-02-22 21:31     ` Gary Thomas
2012-02-22 21:39     ` [oe] " Andreas Müller
2012-02-22 21:39       ` Andreas Müller
2012-02-23 10:11       ` Andreas Müller
2012-02-23 17:50         ` Andreas Müller
2012-02-23 19:18       ` [oe] " Koen Kooi
2012-02-23 19:18         ` [OE-core] " Koen Kooi
2012-02-27 11:37         ` [oe] " Andreas Müller
2012-02-27 12:19           ` Richard Purdie [this message]
2012-02-27 13:31             ` Andreas Müller
2012-02-27 17:09               ` Khem Raj
2012-02-22 20:56 ` Andreas Müller
2012-02-22 20:57   ` Andreas Müller

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=1330345164.4593.18.camel@ted \
    --to=richard.purdie@linuxfoundation.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 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.