Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] image-prelink.bbclass: use the pseudo env var PSEUDO_ALLOW_FSYNC for prelink
Date: Thu, 21 Nov 2013 13:26:00 -0600	[thread overview]
Message-ID: <1385061961-4697-1-git-send-email-mark.hatle@windriver.com> (raw)

From: Jackie Huang <jackie.huang@windriver.com>

(Note: this patch is sent for YP compliance, I don't believe it is
 applicable to general oe-core.)

This would actually emit fsync calls, which may fix the do_rootfs failure
on older systems like CentOS 5.x or SuSE 11.

Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
---
 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..9d7a606 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
+	PSEUDO_ALLOW_FSYNC=1 ${STAGING_DIR_NATIVE}${sbindir_native}/prelink --root ${IMAGE_ROOTFS} -amR -N -c ${sysconfdir}/prelink.conf
 
 	# Remove the prelink.conf if we had to add it.
 	if [ "$dummy_prelink_conf" = "true" ]; then
-- 
1.8.1.2.545.g2f19ada



             reply	other threads:[~2013-11-21 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 19:26 Mark Hatle [this message]
2013-11-21 19:26 ` [PATCH] syslinux: check for __i386__ and __x86_64__ instead of __SIZEOF_POINTER__ Mark Hatle
2013-11-22 13:51   ` Otavio Salvador
2013-11-22 13:42 ` [PATCH] image-prelink.bbclass: use the pseudo env var PSEUDO_ALLOW_FSYNC for prelink Otavio Salvador
2013-11-22 13:47   ` Richard Purdie

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=1385061961-4697-1-git-send-email-mark.hatle@windriver.com \
    --to=mark.hatle@windriver.com \
    --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