mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Junichi Uekawa <dancer@netfort.gr.jp>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-user@lists.sourceforge.net,
	Junichi Uekawa <dancer@netfort.gr.jp>,
	linux-kernel@vger.kernel.org
Subject: Re: [uml-user] 2.6.14.git: user-mode-linux/x86_64 does not build
Date: Sun, 13 Nov 2005 13:46:20 +0900	[thread overview]
Message-ID: <87u0ehyx2b.dancerj%dancer@netfort.gr.jp> (raw)
In-Reply-To: <200511121304.12747.blaisorblade@yahoo.it>

Hi

> > UML does not build from linus's git tree for a while, with the
> > following compilation error.
> 
> Ok, I must start catching up - I have lots of fixes but not yet found the time 
> to re-read and send them. This is one of them.
> 
> > .config is attached later.
> 
> > CONFIG_X86_CMPXCHG=y
> 
> > CONFIG_RWSEM_GENERIC_SPINLOCK=y
> > CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> 
> This is what's causing the error, these options should be mutually exclusive. 
> 
> > CONFIG_64BIT=y
> Arh, this is the problem... I made a mistake for x86_64, and the fix has not 
> yet been sent up. Patch attached.

With your patch it builds now, and somewhat runs, not excercised it enough yet.


A snippet of a log of a functional UML session:
sh-3.00# chroot /home/dancer/i386-chroot/1/ /bin/bash
chroot: cannot run command `/bin/bash': Exec format error
sh-3.00# file /home/dancer/i386-chroot/1/bin/bash
/home/dancer/i386-chroot/1/bin/bash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, dynamically linked (uses shared libs), stripped
sh-3.00# uname -a
Linux (none) 2.6.14-g508862e4 #1 Sun Nov 13 13:30:32 JST 2005 x86_64 GNU/Linux


regards,
	junichi
-- 
dancer@{debian.org,netfort.gr.jp}   Debian Project

  reply	other threads:[~2005-11-13  4:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12  1:46 Junichi Uekawa
2005-11-12 12:04 ` [uml-user] " Blaisorblade
2005-11-13  4:46   ` Junichi Uekawa [this message]
2005-11-13 17:46     ` 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=87u0ehyx2b.dancerj%dancer@netfort.gr.jp \
    --to=dancer@netfort.gr.jp \
    --cc=blaisorblade@yahoo.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-user@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

all inboxes | Powered by JetHome®