From: "Michael Levenhagen" <mjleven@sandia.gov>
To: xen-devel@lists.xensource.com
Subject: mini-os compile error
Date: Thu, 15 Sep 2005 15:30:45 -0600 [thread overview]
Message-ID: <4329E805.6010009@sandia.gov> (raw)
I just downloaded xen-2.0.7-src.tgz and when I try and compile mini-os I
get the following errors
mjleven@sacp957:~/xen-2.0/extras/mini-os> make
[ -e h/xen-public] || ln -sf ../../../xen/include/public h/xen-public
/bin/sh: line 0: [: missing `]'
gcc -fno-builtin -O3 -Wall -Ih/ -Wredundant-decls -Wstrict-prototypes
-Wnested-externs -Wpointer-arith -Winline -ansi -D__ASSEMBLY__ -c head.S
-o head.o
gcc -fno-builtin -O3 -Wall -Ih/ -Wredundant-decls -Wstrict-prototypes
-Wnested-externs -Wpointer-arith -Winline -ansi -D__ASSEMBLY__ -c
entry.S -o entry.o
entry.S:75:3: invalid preprocessing directive #A
entry.S:76:3: invalid preprocessing directive #We
entry.S:77:3: invalid preprocessing directive #during
entry.S:78:3: invalid preprocessing directive #until
entry.S:79:3: invalid preprocessing directive #popping
entry.S:80:3: invalid preprocessing directive #be
entry.S:81:3: invalid preprocessing directive #Although
entry.S:82:3: invalid preprocessing directive #like
entry.S:83:3: invalid preprocessing directive #So
entry.S:84:3: invalid preprocessing directive #existing
entry.S:85:3: invalid preprocessing directive #activation
entry.S:110:3: invalid preprocessing directive #[
entry.S:111:3: invalid preprocessing directive #just
entry.S:112:3: invalid preprocessing directive #region
entry.S:113:3: invalid preprocessing directive #registers
entry.S:114:3: invalid preprocessing directive #'critical_fixup_table'
entry.S:115:3: invalid preprocessing directive #provides
entry.S:116:3: invalid preprocessing directive #interrupted
entry.S:152:3: invalid preprocessing directive #Hypervisor
entry.S:227:3: invalid preprocessing directive #This
entry.S:228:3: invalid preprocessing directive #which
make: *** [entry.o] Error 1
mjleven@sacp957:~/xen-2.0/extras/mini-os>
I can get around this by changing the comment symbols to /* */.
but then I get
mjleven@sacp957:~/xen-2.0/extras/mini-os> make
[ -e h/xen-public] || ln -sf ../../../xen/include/public h/xen-public
/bin/sh: line 0: [: missing `]'
gcc -fno-builtin -O3 -Wall -Ih/ -Wredundant-decls -Wstrict-prototypes
-Wnested-externs -Wpointer-arith -Winline -ansi -D__ASSEMBLY__ -c
entry.S -o entry.o
gcc -fno-builtin -O3 -Wall -Ih/ -Wredundant-decls -Wstrict-prototypes
-Wnested-externs -Wpointer-arith -Winline -ansi -c kernel.c -o kernel.o
kernel.c: In function `start_kernel':
kernel.c:96: error: `EVENTS_MASTER_ENABLE_BIT' undeclared (first use in
this function)
kernel.c:96: error: (Each undeclared identifier is reported only once
kernel.c:96: error: for each function it appears in.)
kernel.c:96: error: structure has no member named `events_mask'
kernel.c:96: error: structure has no member named `events'
kernel.c: At top level:
kernel.c:157: warning: `exit_handler' defined but not used
kernel.c:164: warning: `debug_handler' defined but not used
make: *** [kernel.o] Error 1
mjleven@sacp957:~/xen-2.0/extras/mini-os>
I can't find EVENTS_MASTER_ENABLE_BIT defined anywhere.
I'm running on a SUSE 9.2 Pro. distro.
mjleven@sacp957:~/xen-2.0/extras/mini-os> uname -a
Linux sacp957 2.6.11.12-xen0 #1 Thu Aug 4 00:45:12 BST 2005 i686 i686
i386 GNU/Linux
mjleven@sacp957:~/xen-2.0/extras/mini-os>
mjleven@sacp957:~/xen-2.0/extras/mini-os> gcc -v
Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.4/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada
--disable-checking --libdir=/usr/lib --enable-libgcj
--with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux
Thread model: posix
gcc version 3.3.4 (pre 3.3.5 20040809)
mjleven@sacp957:~/xen-2.0/extras/mini-os> as -v
GNU assembler version 2.15.91.0.2 (i586-suse-linux) using BFD version
2.15.91.0.2 20040727 (SuSE Linux)
mjleven@sacp957:~/xen-2.0/extras/mini-os>
I can build xen, tools and linux26 just fine.
What am I doing wrong?
thanks
Mike
PS. I've tried unstable and I get a completely different compile failure.
reply other threads:[~2005-09-15 21:30 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=4329E805.6010009@sandia.gov \
--to=mjleven@sandia.gov \
--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.