From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Recent OBJDUMP changes
Date: Mon, 04 Dec 2006 13:23:45 +0000 [thread overview]
Message-ID: <1165238625.15272.3.camel@localhost.localdomain> (raw)
In-Reply-To: <c384c5ea0612031500o3ee66a23x89d72a948f418532@mail.gmail.com>
On Mon, 2006-12-04 at 00:00 +0100, Leon Woestenberg wrote:
> 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?
BUILD_OBJDUMP would use BUILD_PREFIX
HOST_OBJDUMP (or OBJDUMP) should use HOST_PREFIX
> OBJDUMP uses HOST_PREFIX, which seems undefined during packaging
> (using package_ipk).
HOST_PREFIX should never be undefined. How are you working out its
undefined?
When running an arm build, HOST_PREFIX might be "arm-linux-" so the
objdump used would be arm-linux-objdump. Note that if arm-linux-objdump
isn't in PATH, that would be a problem.
For comparison BUILD_PREFIX would be "i686-linux-" on my system and
using "i686-linux-objdump" which wouldn't make sense on arm binaries
when packaging.
Cheers,
Richard
next prev parent reply other threads:[~2006-12-04 13:24 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 [this message]
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=1165238625.15272.3.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