Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gdb-cross-sdk: don't reconfigure after making changes in gdb/Makefile
Date: Tue, 02 Nov 2010 13:47:25 -0700	[thread overview]
Message-ID: <4CD078DD.8020504@mentor.com> (raw)
In-Reply-To: <4CD03FCC.6030002@eukrea.com>

Eric Bénard wrote:
> Le 02/11/2010 15:57, Tom Rini a écrit :
>> Can we look at NOT doing the dance we're doing here and instead try 
>> the normal
>> autotools stuff? The "we need to not do ..." stuff looks to be an ancient
>> artifact.
>>
> following the recent changes in this file we have a regression : some 
> libs are no more statically linked in gdb and this patch fix this 
> regression.
> Can we apply it and then we can think on a better way to rewrite these 
> recipes. After a few tries, switching to autotools doesn't work out of 
> the box because gdb is waiting for autoconf 2.64 when we have 2.65.

OK, yes, since you've found it to be non-trivial, it can be done a 
little bit later.  Thanks!

-- 
Tom Rini
Mentor Graphics Corporation



      reply	other threads:[~2010-11-02 20:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01 21:29 [PATCH] gdb-cross-sdk: don't reconfigure after making changes in gdb/Makefile Eric Bénard
2010-11-02  4:41 ` Khem Raj
2010-11-02 14:46   ` Eric Bénard
2010-11-02 14:56     ` [PATCH] gdb-cross-sdk: reconfigure before running oe_runmake configure-host Eric Bénard
2010-11-02 17:56       ` Khem Raj
2010-11-02 20:47         ` Tom Rini
2010-11-02 14:57     ` [PATCH] gdb-cross-sdk: don't reconfigure after making changes in gdb/Makefile Tom Rini
2010-11-02 16:43       ` Eric Bénard
2010-11-02 20:47         ` Tom Rini [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=4CD078DD.8020504@mentor.com \
    --to=tom_rini@mentor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox