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: gdb-cross-canadian fails to build
Date: Wed, 05 Oct 2011 11:12:12 +0100	[thread overview]
Message-ID: <1317809540.14671.128.camel@ted> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E098FD75@orsmsx504.amr.corp.intel.com>

On Tue, 2011-10-04 at 13:48 -0700, Kamble, Nitin A wrote:
> 
> > -----Original Message-----
> > From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
> > Behalf Of Otavio Salvador
> > Sent: Tuesday, October 04, 2011 1:48 PM
> > To: Patches and discussions about the oe-core layer; Kamble, Nitin A
> > Subject: Re: gdb-cross-canadian fails to build
> > 
> > On Tue, Oct 4, 2011 at 17:40, Otavio Salvador <otavio@ossystems.com.br>
> > wrote:
> > ...
> > > Log data follows:
> > > | NOTE: Applying patch 'no-werror.patch'
> > > (openembedded-core/meta/recipes-devtools/gdb/gdb/no-werror.patch)
> > ...
> > > /home/otavio/hacking/ossystems/embedded-linux/openembedded-
> > core/meta/recipes-devtools/gdb/gdb-cross-canadian_7.3.1.bb:
> > ...
> > 
> > It seems to have been broken by:
> > 9002f664383d71682767546524e1299137b6fe4f
> > 
> > Nitin, can you take a look?
> Sure, I will look into it.

I've pushed a fix for this. 

Nitin: This is the second time a gdb upgrade has broken in this way so
please ensure you test cross-canadian in future please!

Cheers,

Richard




      reply	other threads:[~2011-10-05 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 20:40 gdb-cross-canadian fails to build Otavio Salvador
2011-10-04 20:47 ` Otavio Salvador
2011-10-04 20:48   ` Kamble, Nitin A
2011-10-05 10:12     ` 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=1317809540.14671.128.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.