linux-um archives
 help / color / mirror / Atom feed
From: "gboutwel" <gboutwel@praize.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Problems with the SKAS patch and 2.6
Date: 21 Apr 2004 01:11:44 -0000	[thread overview]
Message-ID: <20040421011144.27824.qmail@praize.com> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 733 bytes --]

> Yeah I figured this out, and applied it, but wasn't able to
finish

> compiling an UML guest, started getting error in /usr/innclude/asm

> directory.  Dealing with mpsecc.h, I think this is cause Debian

> (unstable/SID) doesn't have new enough kernel-headers, does
that

> sound about right?



mpsecc.h should be mpspec.h, it acts like it thinks I have an
SMP config, but I don't.  Also, if it wasn't an UML specific
problem, why did the host compile fine, but the guest doesn't?



I'm attaching the 'log' generated by:



make linux ARCH=um 2>&1 | tee uml-2.6.6-rc1.log



HTH,

George



------------------------------------

Want to talk to other Christians?

Get the Christian Instant Messenger

http://www.praize.com/IM/ 

[-- Attachment #2: uml-2.6.6-rc1.log --]
[-- Type: , Size: 3619 bytes --]

  CHK     include/linux/version.h
  UPD     include/linux/version.h
  SYMLINK include/asm -> include/asm-um
  SPLIT   include/linux/autoconf.h -> include/config/*
  HOSTCC  arch/um/sys-i386/util/mk_sc
  HOSTCC  arch/um/kernel/skas/util/mk_ptregs
  Generating /usr/src/linux-2.6.6-rc1/arch/um/include/skas_ptregs.h (updated)
  CHK     arch/um/include/sysdep-i386/sc.h
  UPD     arch/um/include/sysdep-i386/sc.h
cd /usr/src/linux-2.6.6-rc1/include/asm-um && ln -sf ../asm-i386 arch
cd arch/um/include && ln -sf sysdep-i386 sysdep
cd arch/um && ln -sf os-Linux os
cd /usr/src/linux-2.6.6-rc1/include/asm-um/ ; \
ln -sf archparam-i386.h archparam.h
cd /usr/src/linux-2.6.6-rc1/include/asm-um/ ; \
ln -sf system-i386.h system.h
cd /usr/src/linux-2.6.6-rc1/include/asm-um/ ; \
ln -sf sigcontext-i386.h sigcontext.h
cd /usr/src/linux-2.6.6-rc1/include/asm-um/ ; \
ln -sf processor-i386.h processor.h
cd /usr/src/linux-2.6.6-rc1/include/asm-um/ ; \
ln -sf ptrace-i386.h ptrace.h
cd /usr/src/linux-2.6.6-rc1/include/asm-um/ ; \
ln -sf arch-signal-i386.h arch-signal.h
  CHK     arch/um/include/uml-config.h
  UPD     arch/um/include/uml-config.h
  HOSTCC  arch/um/util/mk_constants_kern.o
  HOSTCC  arch/um/util/mk_constants_user.o
  HOSTCC  arch/um/util/mk_task_kern.o
In file included from /usr/include/asm/smp.h:18,
                 from /usr/include/linux/smp.h:17,
                 from /usr/include/linux/sched.h:23,
                 from arch/um/util/mk_task_kern.c:2:
/usr/include/asm/mpspec.h:6:25: mach_mpspec.h: No such file or directory
In file included from /usr/include/asm/smp.h:18,
                 from /usr/include/linux/smp.h:17,
                 from /usr/include/linux/sched.h:23,
                 from arch/um/util/mk_task_kern.c:2:
/usr/include/asm/mpspec.h:8: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/usr/include/asm/mpspec.h:9: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/usr/include/asm/mpspec.h:10: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/usr/include/asm/mpspec.h:12: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/usr/include/asm/mpspec.h:19: error: `MAX_APICS' undeclared here (not in a function)
/usr/include/asm/mpspec.h:20: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/usr/include/asm/mpspec.h:20: error: conflicting types for `mp_bus_id_to_type'
/usr/include/asm/mpspec.h:8: error: previous declaration of `mp_bus_id_to_type'
/usr/include/asm/mpspec.h:22: error: `MAX_IRQ_SOURCES' undeclared here (not in a function)
/usr/include/asm/mpspec.h:24: error: `MAX_MP_BUSSES' undeclared here (not in a function)
/usr/include/asm/mpspec.h:24: error: conflicting types for `mp_bus_id_to_pci_bus'
/usr/include/asm/mpspec.h:12: error: previous declaration of `mp_bus_id_to_pci_bus'
/usr/include/asm/mpspec.h:54: error: `MAX_APICS' undeclared here (not in a function)
In file included from /usr/include/asm/smp.h:20,
                 from /usr/include/linux/smp.h:17,
                 from /usr/include/linux/sched.h:23,
                 from arch/um/util/mk_task_kern.c:2:
/usr/include/asm/io_apic.h:120: error: `MAX_IRQ_SOURCES' undeclared here (not in a function)
/usr/include/asm/io_apic.h:120: error: conflicting types for `mp_irqs'
/usr/include/asm/mpspec.h:22: error: previous declaration of `mp_irqs'
In file included from /usr/include/linux/smp.h:17,
                 from /usr/include/linux/sched.h:23,
                 from arch/um/util/mk_task_kern.c:2:
/usr/include/asm/smp.h:73:26: mach_apicdef.h: No such file or directory
make[1]: *** [arch/um/util/mk_task_kern.o] Error 1
make: *** [arch/um/util] Error 2
\r

             reply	other threads:[~2004-04-21  1:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  1:11 gboutwel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-20 16:31 [uml-devel] Problems with the SKAS patch and 2.6 gboutwel
2004-04-18 18:55 gboutwel
2004-04-19  0:00 ` Jeff Chua
2004-04-19 19:33 ` BlaisorBlade
2004-04-16  6:36 Steven Elliott
2004-04-16  8:19 ` Jeff Chua
2004-04-16 17:28   ` BlaisorBlade

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=20040421011144.27824.qmail@praize.com \
    --to=gboutwel@praize.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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