From: David F Barrera <dfbp@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Another 'make world' problem - unstable changeset 8758
Date: Mon, 06 Feb 2006 10:57:12 -0600 [thread overview]
Message-ID: <43E77FE8.9040302@us.ibm.com> (raw)
Seeing this error on a couple of SLES 9 SP2 boxes.
make CONFIG_FILE=linux-2.6.16-rc2-xen0/.config -f buildconfigs/Rules.mk
config-update-pae
make[4]: Entering directory `/tmp/xen-unstable.hg'
grep '^CONFIG_HIGHMEM64G=y' linux-2.6.16-rc2-xen0/.config >/dev/null &&
( sed -e 's!^CONFIG_HIGHMEM64G=y$!\# CONFIG_HIGHMEM64G is not set!;s!^\#
CONFIG_HIGHMEM4G is not set$!CONFIG_HIGHMEM4G=y!'
linux-2.6.16-rc2-xen0/.config > linux-2.6.16-rc2-xen0/.config- && mv
linux-2.6.16-rc2-xen0/.config- linux-2.6.16-rc2-xen0/.config ) || true
make[4]: Leaving directory `/tmp/xen-unstable.hg'
# Patch kernel Makefile to set EXTRAVERSION
( cd linux-2.6.16-rc2-xen0 ; \
sed -e 's/^EXTRAVERSION.*/&$(XENGUEST)\nXENGUEST = -xen0/' Makefile
>Mk.tmp ; \
rm -f Makefile ; mv Mk.tmp Makefile )
make -C linux-2.6.16-rc2-xen0 ARCH=i386 oldconfig
make[4]: Entering directory `/tmp/xen-unstable.hg/linux-2.6.16-rc2-xen0'
.config:3: *** missing separator. Stop.
make[4]: *** [scripts_basic] Error 2
make[4]: Leaving directory `/tmp/xen-unstable.hg/linux-2.6.16-rc2-xen0'
make[3]: *** [linux-2.6.16-rc2-xen0/include/linux/autoconf.h] Error 2
make[3]: Leaving directory `/tmp/xen-unstable.hg'
make[2]: *** [linux-2.6-xen0-install] Error 2
make[2]: Leaving directory `/tmp/xen-unstable.hg'
make[1]: *** [install-kernels] Error 1
make[1]: Leaving directory `/tmp/xen-unstable.hg'
make: *** [world] Error 2
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
reply other threads:[~2006-02-06 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43E77FE8.9040302@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=xen-devel@lists.xensource.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 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.