From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Recent OBJDUMP changes
Date: Mon, 04 Dec 2006 11:30:11 +0100 [thread overview]
Message-ID: <4573F8B3.3070207@dominion.kabel.utwente.nl> (raw)
In-Reply-To: <c384c5ea0612031500o3ee66a23x89d72a948f418532@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Leon Woestenberg schreef:
> Hello,
>
> I seem to hit upon a recent change involving finding shlib
> dependencies using the objdump | grep NEEDED approach by Graeme
> Gregory/XorA:
>
> http://www.openembedded.org/viewmtn/revision.psp?id=1fb8812d36f505cfabe9ee2335441ada60e32f83
>
> Shouldn't (BUILD_)OBJDUMP be defined instead with a BUILD_PREFIX?
>
> OBJDUMP uses HOST_PREFIX, which seems undefined during packaging
> (using package_ipk).
I have something like this:
- --- conf/bitbake.conf a55e0d456ecb5fa95185e35580c90bcc9513ed8d
+++ conf/bitbake.conf e3d238d78a95629037ad0f48ce24e3a7382e540e
@@ -454,3 +454,6 @@ COMBINED_FEATURES = "\
${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "usbgadget", d)} \
${@base_both_contain("DISTRO_FEATURES", "MACHINE_FEATURES", "usbhost", d)}"
+
+export OBJDUMP := "${HOST_PREFIX}objdump"
+
That should fix the issues, but isn't the right way.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFc/izMkyGM64RGpERAjhhAJ0f60RLRLZFi85k9fKplwcNEFDW5QCgiNAp
uIxZ+fPMroGwGqnpXg63Fww=
=C+Oa
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-12-04 10:31 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 [this message]
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
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=4573F8B3.3070207@dominion.kabel.utwente.nl \
--to=koen@dominion.kabel.utwente.nl \
--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