Your message dated Fri, 28 Apr 2006 18:34:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug #200325: user-mode-linux: Source compilation fails with 
kernel-source-2.4.18_2.4.18-9 (kernel_thread)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: user-mode-linux
Version: 2.4.18.17um-1
Severity: normal
Tags: patch

The source of user-mode-linux 2.4.18.17um-1 (current stable uml) when
applied to kernel-source-2.4.18_2.4.18-9 (the current stable kernel
source) produces a kernel that can not be compiled:

gcc -D__KERNEL__
-I/root/installs/user-mode-linux-2.4.18.17um/kernel-source-2.4.18/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common   -U__i386__ -Ui386 -DUM_FASTCALL
-D__arch_um__ -DSUBARCH=\"i386\" -DNESTING=0 -D_LARGEFILE64_SOURCE
-I/root/installs/user-mode-linux-2.4.18.17um/kernel-source-2.4.18/arch/um/include
-Derrno=kernel_errno -c mk_task_kern.c
In file included from mk_task_kern.c:1:
/root/installs/user-mode-linux-2.4.18.17um/kernel-source-2.4.18/include/linux/sched.h:799:
conflicting types for `kernel_thread'
/root/installs/user-mode-linux-2.4.18.17um/kernel-source-2.4.18/include/asm/processor-generic.h:95:
previous declaration of `kernel_thread'
make[1]: *** [mk_task_kern.o] Error 1

...

It seems that as of kernel-source-2.4.18_2.4.18-9 there is a generic
kernel_thread() defined in kernel/fork.c (line 557) and the architecture
speciffic implementation is left for arch_kernel_thread() - function
defined in arch/um/kernel/process_kern.c and declared in
arch/um/include/asm-um/processor-generic.h


Here is a patch that can be applied to uml-patch-2.4.18-13
(compressed in uml-patch-2.4.18-13.gz and part of the source
package):

--- uml-patch-2.4.18-13.original        Sun Jul  6 23:53:05 2003
+++ uml-patch-2.4.18-13 Sun Jul  6 23:56:44 2003
@@ -16083,7 +16083,7 @@
 +      usr1_pid(getpid());
 +}
 +
-+int kernel_thread(int (*fn)(void *), void * arg, unsigned long flags)
++int arch_kernel_thread(int (*fn)(void *), void * arg, unsigned long flags)
 +{
 +      int pid;
 +
@@ -25913,7 +25913,7 @@
 +#define get_task_struct(tsk)      atomic_inc(&virt_to_page(tsk)->count)
 +
 +extern void release_thread(struct task_struct *);
-+extern int kernel_thread(int (*fn)(void *), void * arg, unsigned long
flags);
++extern int arch_kernel_thread(int (*fn)(void *), void * arg, unsigned long
flags);
 +
 +static inline void release_segments(struct mm_struct *mm)
 +{



After appluing this patch I was able to recompile and use uml.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux VKP3500 2.4.18 #3 Fri JUL 4 22:42:29 CST 2003 i686

Versions of packages user-mode-linux depends on:
ii  uml-utilities                 20020415-3 User-mode Linux (utility
programs)

=====
Yet Another Thawte Notary. For a free personal digital certificate visit 
www.thawte.com

The text below was appended by the mailbox service provider so I should not be 
held responsible for it. Vesselin.

http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.


--- End Message ---
--- Begin Message ---
package user-mode-linux
severity 200325 serious
close 200325
thanks

Dear all,
since 2.4 u-m-l support is no more available in the upcoming releases,
I should say that the bug #200325 can be closed.

Cheers

SteX
-- 
Stefano Melchior, GPG key = D52DF829 - <[EMAIL PROTECTED]>
http://etinarcadiaego.dyndns.org    --     http://www.stex.name
Skype ID "stefanomelchior"

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to