From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] nss:fix postinst failed at rootfs time
Date: Wed, 24 Jul 2013 13:31:57 +0800 [thread overview]
Message-ID: <51EF66CD.5030503@windriver.com> (raw)
In-Reply-To: <CAJTo0LaLCLNXT5hEjTW6HNq+S++VvC+JjRoLtszYfMJ+HNJkQQ@mail.gmail.com>
On 07/23/2013 10:48 PM, Burton, Ross wrote:
> On 22 July 2013 06:45, Hongxu Jia <hongxu.jia@windriver.com> wrote:
>> Create checksum file at rootfs time to support read-only rootfs.
> Have you verified that the checksum files don't change depending on
> the host architecture (big/little endian, 32/64 bit)?
Yes, I have verified.
*host
BUILD_SYS = "x86_64-linux"
*target
TARGET_SYS = "mips-poky-linux"
MACHINE = "qemumips"
or
TARGET_SYS = "i586-poky-linux"
MACHINE = "qemux86"
Everything is ok.
Thanks,
Hongxu
> Ross
next prev parent reply other threads:[~2013-07-24 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 5:45 [PATCH 0/1] nss:fix postinst failed at rootfs time Hongxu Jia
2013-07-22 5:45 ` [PATCH 1/1] " Hongxu Jia
2013-07-23 14:48 ` Burton, Ross
2013-07-24 5:31 ` Hongxu Jia [this message]
2013-07-23 11:24 ` [PATCH 0/1] " Hongxu Jia
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=51EF66CD.5030503@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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