From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Nathan West <nathan.west@okstate.edu>
Subject: Re: [PATCH] point prelink.conf to ${IMAGE_ROOTFS}
Date: Tue, 17 Jul 2012 17:48:17 -0700 [thread overview]
Message-ID: <500607D1.1010009@linux.intel.com> (raw)
In-Reply-To: <CACFtY++ekHacLd5VLvfEabKxkdTFxSzfa6oU+aRbS5br_PzDxA@mail.gmail.com>
On 07/17/2012 03:16 PM, Nathan West wrote:
> Hopefully I do this right. First time patching (ever! this is exciting :-) )
>
Welcome to the wonderful world of patching!
> The --root option doesn't work and isn't documented anywhere I could
> find, and without the ${IMAGE_ROOTFS} before the config file it was
> point to my native /etc/prelink.conf (which doesn't exist and probably
> would be useful if it did)
>
Which prelink are you using, it's possible you did not look at the
correct one.
There should be a tmp/sysroot/x86_64-linux/usr/sbin/prelink (if you are
building on a 64bit machine, otherwise i586-linux), that's the prelink
binary and a --help to that will show the --root option.
It should not be using your host's /etc/prelink.conf, but the sysroot
version.
The --root option should take care of it as it's described as follows:
--root=ROOT_PATH Prefix all paths with ROOT_PATH
So, the next question is what's going on to cause it to use your host's
prelinker instead of the native version that should be build as part of
the native tools?
> Be gentle if I screwed up!
No worries.
> -Nathan
>
Hope that was not too painful, let see how we can help you accomplish
what you are trying to do.
Sau!
>
>
> ---
> meta/classes/image-prelink.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/image-prelink.bbclass
> b/meta/classes/image-prelink.bbclass
> index 53ef47e..2d62f03 100644
> --- a/meta/classes/image-prelink.bbclass
> +++ b/meta/classes/image-prelink.bbclass
> @@ -21,7 +21,7 @@ prelink_image () {
> fi
> # prelink!
> -${STAGING_DIR_NATIVE}${sbindir_native}/prelink --root ${IMAGE_ROOTFS}
> -amR -N -c ${sysconfdir}/prelink.conf
> +${STAGING_DIR_NATIVE}${sbindir_native}/prelink ${IMAGE_ROOTFS} -amR -N
> -c ${IMAGE_ROOTFS}${sysconfdir}/prelink.conf
> # Remove the prelink.conf if we had to add it.
> if [ "$dummy_prelink_conf" = "true" ]; then
> --
> 1.7.9.5
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-07-18 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 22:16 [PATCH] point prelink.conf to ${IMAGE_ROOTFS} Nathan West
2012-07-18 0:48 ` Saul Wold [this message]
[not found] ` <CACFtY+KW+VfCKmaWTkO5vjw3k7fmR2Awfb31YUZc2cAhXCEi0A@mail.gmail.com>
2012-07-18 13:26 ` Nathan West
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=500607D1.1010009@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=nathan.west@okstate.edu \
--cc=openembedded-core@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