From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] kernel.bbclass: fix hardlink test
Date: Sat, 16 Nov 2013 01:17:23 -0500 [thread overview]
Message-ID: <cover.1384582409.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
It's sometimes nice when you get to clean up your own mess. While all my
build tests passed on Friday to fix the "vmlinux" and "usr/src/kernel/vmlinux"
are the same file, it was because the install failed in all cases, not just
the one we wanted to prevent.
I bumped into a build failure when assembling xen hdmimage, since it could
find the bzImage in the kernel source directory. I tracked it back to
the hardlink fix, and on debugging, noticed that the test wasn't good on
all machines.
An extra space fixes everything up, and I'm now able to build my xen image
AND build linux-yocto for qemumips, and another other target you should
favour.
Take this for spin .. since it is late at night when I did this, but it
should be fine :)
Cheers,
Bruce
The following changes since commit db7f8d4114267ed34c19dc66dd56c2372354b43f:
kernel.bbclass: test for hardlinks before installing (2013-11-15 15:27:08 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
kernel.bbclass: fix hardlink test
meta/classes/kernel.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.8.1.2
next reply other threads:[~2013-11-16 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 6:17 Bruce Ashfield [this message]
2013-11-16 6:17 ` [PATCH 1/1] kernel.bbclass: fix hardlink test Bruce Ashfield
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=cover.1384582409.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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