All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Hans Peter Freyther <holger@freyther.de>
To: poky@yoctoproject.org
Subject: kernel upgrade breaks image creation
Date: Sun, 03 Jul 2011 10:34:20 +0200	[thread overview]
Message-ID: <4E10298C.8080507@freyther.de> (raw)

Hi all,

I managed to get my build directory into an inconsistent state. There was a
kernel update and now the image fails to be built. It tries to copy the
System.map-... from the sysroot/${MACHINE}/kernel/... but it is empty:

| FATAL: Could not open
'/poky/build/tmp/sysroots/sysmocom-foo/kernel/System.map-2.6.33-07172-g57e3d92':
No such file or directory
| FATAL: Could not open
'/poky/build/tmp/sysroots/sysmocom-foo/kernel/System.map-2.6.33-07172-g57e3d92':
No such file or directory
| FATAL: Could not open
'/poky/build/tmp/sysroots/sysmocom-foo/kernel/System.map-2.6.33-07172-g57e3d92':
No such file or directory
| FATAL: Could not open
'/poky/build/tmp/sysroots/sysmocom-foo/kernel/System.map-2.6.33-07172-g57e3d92':
No such file or directory


I tried a bitbake -cclean virtual/kernel, also a cleanall, interestingly the
sysmocom-ti/kernel directory is not removed or does not seem to be
re-populated. Did anyone else ever see that behavior? There was one non
standard thing in the kernel upgrade:

+PR... bumped
-SRC_URI = "git://linux.git;protocol=ssh;branch=master"
+SRC_URI = "git://linux.git;protocol=ssh;branch=master \
+          file://defconfig-${MACHINE}"
 S = "${WORKDIR}/git"

 do_configure() {
-       oe_runmake foo_defconfig
-       oe_runmake oldconfig
+       install -m 0644 ${WORKDIR}/defconfig-${MACHINE} ${S}/.config
+       #oe_runmake foo_defconfig
+       #oe_runmake oldconfig
 }

is there anything that makes click?

	holger


             reply	other threads:[~2011-07-03  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03  8:34 Holger Hans Peter Freyther [this message]
2011-07-03  9:11 ` kernel upgrade breaks image creation Richard Purdie
2011-07-03 12:24   ` Holger Hans Peter Freyther

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=4E10298C.8080507@freyther.de \
    --to=holger@freyther.de \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.