From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>, Anthony Brock <Anthony_Brock@ous.edu>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Problems compiling 2.4 kernel
Date: Thu, 1 Jul 2004 19:36:11 +0200 [thread overview]
Message-ID: <200407011936.11144.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200407011643.i61GhRl9002573@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
Alle 18:43, giovedì 1 luglio 2004, Jeff Dike ha scritto:
> Anthony_Brock@ous.edu said:
The problem is another: uml Makefile don't manage properly the
include/asm/arch symlink, and it is not created:
> asm/arch/posix_types.h: No such file or directory
To workaround this:
cd include
<make sure that asm points to asm-um>
cd asm
ln -s ../asm-i386 arch
There is a lot of other people claiming similar problems. For instance,
somebody else complained that to build UML he must avoid doing "make mrproper
ARCH=um" because some files are not recreated (with 2.4.24-3).
However, Anthony, I would recommend using, for optimal stability, a 2.4.26
vanilla kernel patched with 2.4.24-1um + the attached patch.
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
[-- Attachment #2: uml-2.4.26-cmpxchg.patch --]
[-- Type: text/x-diff, Size: 1049 bytes --]
--- linux-2.4.26/include/asm-um/system-i386.h Wed Apr 21 15:33:45 2004
+++ linux-2.4.26-umlfix/include/asm-um/system-i386.h Wed Apr 21 15:27:14 2004
@@ -5,35 +5,4 @@
#define __HAVE_ARCH_CMPXCHG 1
-static inline unsigned long __cmpxchg(volatile void *ptr, unsigned long old,
- unsigned long new, int size)
-{
- unsigned long prev;
- switch (size) {
- case 1:
- __asm__ __volatile__(LOCK_PREFIX "cmpxchgb %b1,%2"
- : "=a"(prev)
- : "q"(new), "m"(*__xg(ptr)), "0"(old)
- : "memory");
- return prev;
- case 2:
- __asm__ __volatile__(LOCK_PREFIX "cmpxchgw %w1,%2"
- : "=a"(prev)
- : "q"(new), "m"(*__xg(ptr)), "0"(old)
- : "memory");
- return prev;
- case 4:
- __asm__ __volatile__(LOCK_PREFIX "cmpxchgl %1,%2"
- : "=a"(prev)
- : "q"(new), "m"(*__xg(ptr)), "0"(old)
- : "memory");
- return prev;
- }
- return old;
-}
-
-#define cmpxchg(ptr,o,n)\
- ((__typeof__(*(ptr)))__cmpxchg((ptr),(unsigned long)(o),\
- (unsigned long)(n),sizeof(*(ptr))))
-
#endif
next prev parent reply other threads:[~2004-07-01 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 15:30 [uml-devel] Problems compiling 2.4 kernel Anthony Brock
2004-07-01 16:43 ` Jeff Dike
2004-07-01 17:36 ` BlaisorBlade [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-01 16:04 Anthony Brock
2004-07-01 16:13 Anthony Brock
2004-07-01 17:40 Anthony Brock
2004-07-01 21:05 ` 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=200407011936.11144.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=Anthony_Brock@ous.edu \
--cc=jdike@addtoit.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