linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: gboutwel <gboutwel@praize.com>
Subject: Re: [uml-devel] Still can't get an 2.6.6-rcX UML
Date: Fri, 30 Apr 2004 16:07:24 +0200	[thread overview]
Message-ID: <200404301607.24027.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040425183446.27642.qmail@praize.com>

Alle 20:34, domenica 25 aprile 2004, gboutwel ha scritto:
> Hello,
>
>   On Debian Unstable/SID.  I do the following, I've done it several
> different ways for rc2 and rc1 and always I get hung up at the
> same point on the UML, I can compile patch and compile the host
> without problem.  This will be the first time since toying with
> UMl and 2.6 kernels that I haven't beenable to get an UML compiled.

>
> make linux ARCH=um
> // this is where it fails.  I fails on the
> // arch/um/util/mk_task_kern.o, #include "linux/sched.h" line
> // which then includes "userspace" includes, which I don't feel
> // comfortable modifying since they are part of my distro and
> // not sure how that would break other applications.

Well, something has been *really* been messed up. If I understand things 
properly, you are able to compile fine a 2.6.5 UML, right?

The problem is that:
a) I think that file should include the "kernelspace" headers... however the 
kludges needed to do it are very fragile when Kbuild changes a bit (this 
problem has repeatedly showed up against Linux 2.6).

However, things should succeed anyway, BUT

b) your distro headers are messed up...; the first thing I see is that it uses 
the 2.6 headers. Now, the missing header should be located in 
/usr/include/asm/mach-default/. Probably it is there; however the kernel uses 
normally a -Iasm/mach-default, so that #include <mach_mpspec.h> works.
Since one cannot require user programs to add -I to compile, Debian should 
symlink everything from /usr/include/asm/mach-default/ into /usr/include; 
i.e.:
ln -s  /usr/include/asm/mach-default/* /usr/include.

Then retry the build, and also watch this thread:

"[uml-devel] patch for 2.6.6-rc1".

Bye and HTH!
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-04-30 16:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-25 18:34 [uml-devel] Still can't get an 2.6.6-rcX UML gboutwel
2004-04-26  1:50 ` Jeff Chua
2004-04-30 14:07 ` BlaisorBlade [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-26 13:46 gboutwel
2004-04-26 18:58 gboutwel
2004-04-30 18:31 gboutwel
2004-04-30 18:58 ` BlaisorBlade
2004-05-04 20:05 gboutwel
2004-05-11 17:35 ` BlaisorBlade
2004-05-12 15:35 gboutwel

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=200404301607.24027.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=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