Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Michael Morscher <michael.morscher@hs-augsburg.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gdb: upgrade from 7.3 to 7.3a
Date: Wed, 31 Aug 2011 15:16:08 +0200	[thread overview]
Message-ID: <4E5E3418.3000304@hs-augsburg.de> (raw)
In-Reply-To: <1314747825.5939.449.camel@rex>

Hey Richard,

Thanks for your patch for gdb, but gdb-cross-canadian is also broken:

Log data follows:
| NOTE: Applying patch 'no-werror.patch' 
(../meta/recipes-devtools/gdb/gdb/no-werror.patch)
| ERROR: Error executing a python function in 
/build/oe-core/meta/recipes-devtools/gdb/gdb-cross-canadian_7.3a.bb:
| CmdError: Command Error: exit status: 1  Output:
| Applying patch no-werror.patch
| patching file bfd/warning.m4
| Hunk #1 FAILED at 23.
| 1 out of 1 hunk FAILED -- rejects in file bfd/warning.m4
| patching file configure.ac
| Hunk #1 FAILED at 3371.
| 1 out of 1 hunk FAILED -- rejects in file configure.ac
| patching file gdb/Makefile.in
| Hunk #1 FAILED at 151.
| 1 out of 1 hunk FAILED -- rejects in file gdb/Makefile.in
| patching file gdb/configure.ac
| Hunk #1 FAILED at 1525.
| Hunk #2 FAILED at 1587.
| 2 out of 2 hunks FAILED -- rejects in file gdb/configure.ac
| Patch no-werror.patch does not apply (enforce with -f)
|
| ERROR: The stack trace of python calls that resulted in this 
exception/failure was:
| ERROR:   File "patch_do_patch", line 136, in <module>
| ERROR:
| ERROR:   File "patch_do_patch", line 133, in patch_do_patch
| ERROR:
| ERROR:   File "/build/oe-core/meta/lib/oe/patch.py", line 338, in Resolve
| ERROR:     raise sys.exc_value
| ERROR:
| ERROR: The code that was being executed was:
| ERROR:      0132:                     raise 
bb.build.FuncFailed(str(sys.exc_value))
| ERROR:      0133:             resolver.Resolve()
| ERROR:      0134:
| ERROR:      0135:
| ERROR:  *** 0136:patch_do_patch(d)
| ERROR:      0137:
| ERROR: (file: 'patch_do_patch', lineno: 136, function: <module>)
| ERROR:      0129:                     patchset.Import({"file":local, 
"remote":url, "strippath": striplevel}, True)
| ERROR:      0130:             except Exception:
| ERROR:      0131:                     import sys
| ERROR:      0132:                     raise 
bb.build.FuncFailed(str(sys.exc_value))
| ERROR:  *** 0133:             resolver.Resolve()
| ERROR:      0134:
| ERROR:      0135:
| ERROR:      0136:patch_do_patch(d)
| ERROR:      0137:
| ERROR: (file: 'patch_do_patch', lineno: 133, function: patch_do_patch)
| ERROR: Function 'patch_do_patch' failed
NOTE: package gdb-cross-canadian-arm-7.3a-r4.0: task do_patch: Failed


Bye




  parent reply	other threads:[~2011-08-31 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 13:13 [PATCH] gdb: upgrade from 7.3 to 7.3a Sebastian Krzyszkowiak
2011-08-30 21:13 ` Richard Purdie
2011-08-30 22:12   ` Michael Morscher
2011-08-30 22:18     ` Sebastian Krzyszkowiak
2011-08-30 23:43       ` Richard Purdie
2011-08-31  9:40         ` Sebastian Krzyszkowiak
2011-08-31 13:16         ` Michael Morscher [this message]
2011-08-31 18:46           ` 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=4E5E3418.3000304@hs-augsburg.de \
    --to=michael.morscher@hs-augsburg.de \
    --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