All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoffrey Wossum <geoffrey@pager.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: avr32-*-gdb requires modifying gdb.inc / gdb-cross.inc
Date: Wed, 9 Apr 2008 10:49:58 -0500	[thread overview]
Message-ID: <200804091049.58718.geoffrey@pager.net> (raw)
In-Reply-To: <1207753641.7368.20.camel@isis>

On Wednesday 09 April 2008 10:07:21 am Khem Raj wrote:
> Hi Geoffrey
>
> I think it will be good to make this step arch specific to AVR only.
> and best is to identify what changes are done in configure that needs it
> to be regenerated. You can regenerate these and include them in the
> patch itself instead of doing it at compile time.

Here's Atmel's reasoning for not including all the generated source / 
autotools cruft in the patch:
"The reason why these changes aren't included with the patch is that it would 
have increased its size by several megabytes, and the actual AVR32 changes 
would have been lost in the noise."

Those are good points on their part, plus I don't want to have to create and 
maintain my own patch.  When Atmel comes out with their next gdb, I don't 
want to have to create a new patch based on theirs to include in OE.  I want 
to download their patch and copy it into the OE tree.

This leaves running these extra steps only for the AVR32.  What would I put 
around these extra steps in do_configure() and do_stage() so that they are 
only run when building for the AVR32.

---
Geoffrey



      reply	other threads:[~2008-04-09 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 14:20 avr32-*-gdb requires modifying gdb.inc / gdb-cross.inc Geoffrey Wossum
2008-04-09 15:07 ` Khem Raj
2008-04-09 15:49   ` Geoffrey Wossum [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=200804091049.58718.geoffrey@pager.net \
    --to=geoffrey@pager.net \
    --cc=openembedded-devel@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.