Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Recent OBJDUMP changes
Date: Fri, 15 Dec 2006 09:09:22 +0000	[thread overview]
Message-ID: <1166173763.5437.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200612121628.07309.openembedded@hrw.one.pl>

On Tue, 2006-12-12 at 16:28 +0100, Marcin Juszkiewicz wrote:
> Does someone found better fix then mine?
> 
> [hrw@misc1 classes]$ mtn dif package.bbclass
> --- classes/package.bbclass     b4538ccc18abcaa057513563f37b2d25fdce5784
> +++ classes/package.bbclass     969285b9af2e3bc59048d34cf396dd529e496c1e
> @@ -576,6 +576,7 @@ python package_do_shlibs() {
>                                 path = os.path.join(root, file)
>                                 if os.access(path, os.X_OK) or lib_re.match(file):
>                                         cmd = bb.data.getVar('OBJDUMP', d, 1) + " -p " + path + " 2>/dev/null"
> +                                       cmd = "PATH=\"%s\" %s" % (bb.data.getVar('PATH', d, 1), cmd)
>                                         fd = os.popen(cmd)
>                                         lines = fd.readlines()
>                                         fd.close()

FWIW, this is the correct fix. Ideally, bitbake should have some helper
functions to set up PATH and run a program but at the moment it doesn't
so we need to do this.

Cheers,

Richard




  reply	other threads:[~2006-12-15  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 23:00 Recent OBJDUMP changes Leon Woestenberg
2006-12-04 10:30 ` Koen Kooi
2006-12-04 13:24   ` Richard Purdie
2006-12-04 13:23 ` Richard Purdie
2006-12-04 20:34   ` Leon Woestenberg
2006-12-12 15:28     ` Marcin Juszkiewicz
2006-12-15  9:09       ` Richard Purdie [this message]
2006-12-19 19:43         ` test - please ignore Stelios Koroneos

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=1166173763.5437.1.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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