All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Martin <antoine@nagafix.co.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, Majid Salame <msalame@nortel.com>
Subject: Re: [uml-devel] NPTL support
Date: Tue, 29 Nov 2005 21:00:42 +0000	[thread overview]
Message-ID: <1133298043.13162.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20051129162801.4474EF3DC@sc8-sf-spam2.sourceforge.net>

> >  Is NPTL supported and working? Are there separate patches to be
> applied
> > against 2.6.10 kernel?
> 
> My current patchset, against 2.5.15-rc1, is running current Debian and
> FC4
> filesystems without any apparent problems.
> 
>                                 Jeff
I thought that last time I failed to build it, Gentoo was to blame so I
tried again today on an amd64 FC4 host, and that worked for i386.
Again, I had to delete the empty files to get that far.

I also had to remove 3-level page tables option, otherwise I get this:
  HOSTCC  scripts/bin2c
  CC      init/main.o
In file included from include/asm/pgtable.h:30,
                 from include/linux/bootmem.h:7,
                 from init/main.c:30:
include/asm/pgtable-3level.h: In function ‘pud_clear’:
include/asm/pgtable-3level.h:74: warning: implicit declaration of
function ‘set_64bit’
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
(...) Lots more warnings about set_64bit... Then the build fails.


Any fix for the GCC errors on arch/um/include/sysdep/stub.h would be
much appreciated (I have to compile on these hosts to be able to use the
pcap network driver):
  CC      arch/um/kernel/skas/clone.o
arch/um/kernel/skas/clone.c: In function `stub_clone_handler':
arch/um/include/sysdep/stub.h:41: error: can't find a register in class
`BREG' while reloading `asm'
arch/um/include/sysdep/stub.h:62: error: can't find a register in class
`BREG' while reloading `asm'
arch/um/include/sysdep/stub.h:51: error: can't find a register in class
`BREG' while reloading `asm'
arch/um/include/sysdep/stub.h:84: error: can't find a register in class
`BREG' while reloading `asm'
make[2]: *** [arch/um/kernel/skas/clone.o] Error 1
make[1]: *** [arch/um/kernel/skas] Error 2
make: *** [arch/um/kernel] Error 2

Or shall I bug the GCC guys?

Thanks
Antoine




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&opΜk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

       reply	other threads:[~2005-11-29 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051129162801.4474EF3DC@sc8-sf-spam2.sourceforge.net>
2005-11-29 21:00 ` Antoine Martin [this message]
2005-11-29 23:14   ` [uml-devel] NPTL support Rob Landley
2005-12-02  0:29   ` Blaisorblade
     [not found] <29D15BBCA340DA4D8146D38B4924FC7A03378F16@zcarhxm0.corp.nortel.com>
2005-11-28 18:27 ` Jeff Dike

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=1133298043.13162.18.camel@localhost.localdomain \
    --to=antoine@nagafix.co.uk \
    --cc=jdike@addtoit.com \
    --cc=msalame@nortel.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 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.