From: Jiri Olsa <olsajiri@gmail.com>
To: Karol Swietlicki <magotari@gmail.com>
Cc: Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [uml-devel] uml doesn't work on 2.6.24-rc2
Date: Fri, 23 Nov 2007 11:54:41 +0100 [thread overview]
Message-ID: <4746B171.1070001@gmail.com> (raw)
In-Reply-To: <ea9232d10711230101j24e4bd4btce65e62b9fcc8f8b@mail.gmail.com>
Hi,
after applying following changes, the mainline is working for me.
Jiri Olsa
diff --git a/arch/um/Kconfig.i386 b/arch/um/Kconfig.i386
index e0ac74e..234fcb4 100644
--- a/arch/um/Kconfig.i386
+++ b/arch/um/Kconfig.i386
@@ -8,6 +8,13 @@ config UML_X86
bool
default y
+config X86_32
+ bool
+ default y
+
+config RWSEM_XCHGADD_ALGORITHM
+ def_bool y
+
config 64BIT
bool
default n
diff --git a/arch/um/Makefile b/arch/um/Makefile
index 31999bc..ba6813a 100644
--- a/arch/um/Makefile
+++ b/arch/um/Makefile
@@ -168,7 +168,7 @@ ifneq ($(KBUILD_SRC),)
$(Q)mkdir -p $(objtree)/include/asm-um
$(Q)ln -fsn $(srctree)/include/asm-$(HEADER_ARCH) include/asm-um/arch
else
- $(Q)cd $(TOPDIR)/include/asm-um && ln -fsn ../asm-$(SUBARCH) arch
+ $(Q)cd $(TOPDIR)/include/asm-um && ln -fsn ../asm-$(HEADER_ARCH) arch
endif
$(objtree)/$(ARCH_DIR)/include:
Karol Swietlicki wrote:
> On 23/11/2007, Jeff Dike <jdike@addtoit.com> wrote:
>> On Thu, Nov 22, 2007 at 07:08:47PM +0100, Miklos Szeredi wrote:
>>> Thanks. My other problem is (probably you are aware) that recent -mm
>>> kernels don't compile for UML.
>> The patch below fixes the build for rc3-mm1 for me.
>>
>> Jeff
>
> There must be something more to it. I got a clean -mm and it still
> does not build after applying the patch. It does have less problems,
> but it still won't build. I tried to get it to compile for half an
> hour, but considering the amount of sleep I got (and my experience),
> there is no surprise that I failed miserably. After fixing the
> complaint about a structure not having a 'x86' member, it died in the
> linker complaining about stuff relating to rwsem.h.
>
> Karol Swietlicki
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
>
next prev parent reply other threads:[~2007-11-23 10:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 23:32 uml doesn't work on 2.6.24-rc2 Miklos Szeredi
2007-11-14 1:10 ` Jeff Dike
2007-11-14 10:35 ` Miklos Szeredi
2007-11-14 14:22 ` Jeff Dike
2007-11-14 15:26 ` Miklos Szeredi
2007-11-14 17:36 ` Jeff Dike
2007-11-14 21:29 ` Miklos Szeredi
2007-11-16 17:06 ` Jeff Dike
2007-11-22 18:08 ` Miklos Szeredi
2007-11-22 23:51 ` Jeff Dike
2007-11-23 8:59 ` Miklos Szeredi
2007-11-23 9:01 ` [uml-devel] " Karol Swietlicki
2007-11-23 10:54 ` Jiri Olsa [this message]
2007-11-23 11:00 ` WANG Cong
2007-11-26 17:47 ` Jeff Dike
2007-11-26 18:10 ` Jeff Dike
2007-11-26 20:52 ` Jeff Dike
2007-11-26 21:22 ` Miklos Szeredi
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=4746B171.1070001@gmail.com \
--to=olsajiri@gmail.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magotari@gmail.com \
--cc=miklos@szeredi.hu \
--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