All of lore.kernel.org
 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 07:57:28 -0700	[thread overview]
Message-ID: <4CD026D8.2030101@mentor.com> (raw)
In-Reply-To: <4CD02461.3020106@eukrea.com>

Eric Bénard wrote:
> Le 02/11/2010 05:41, Khem Raj a écrit :
>> On Mon, Nov 1, 2010 at 2:29 PM, Eric Bénard<eric@eukrea.com>  wrote:
>>> else we don't statically link libncurses, libtinfo and libz which leads
>>> to :
>>> /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-gdb:
>>> error while loading shared libraries: libtinfo.so.5:
>>> cannot open shared object file: No such file or directory
>>>
>>> when trying to use the toolchain.
>>
>> could you run oe_runconf and then do the Makefile editing ? that way
>> it will work as expected.
>> we sort of need oe_runconf
>>
> the makefile we hack with sed is not created after oe_runconf, it's 
> generated by oe_runmake configure-host
> So what should work is :
> oe_runconf
> oe_runmake
> then sed

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.

-- 
Tom Rini
Mentor Graphics Corporation



  parent reply	other threads:[~2010-11-02 14:59 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     ` Tom Rini [this message]
2010-11-02 16:43       ` [PATCH] gdb-cross-sdk: don't reconfigure after making changes in gdb/Makefile Eric Bénard
2010-11-02 20:47         ` Tom Rini

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=4CD026D8.2030101@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 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.