WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] xen 2.0.7 / gcc 3.4 / iptables 1.3.3

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen 2.0.7 / gcc 3.4 / iptables 1.3.3
From: "Jorge I. Davila L." <davila@xxxxxxxxxxxxxxx>
Date: Mon, 10 Oct 2005 06:43:42 -0600
Delivery-date: Mon, 10 Oct 2005 12:40:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi list!:

I'm trying to compile a 2.0.7 xen kernel in a fedora core 3.

The kernel of the dom0 is a 2.6.11.12-xen0 and is required for an
specific application a 2.4 kernel for the domU.

Well ... after a system update I have a compiler 

# gcc --version
gcc (GCC) 3.4.4 20050721 (Red Hat 3.4.4-2)


This a new error ..

make[1]: Entering directory
`/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/crypto'
make all_targets
make[2]: Entering directory
`/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/crypto'
make[2]: Nothing to be done for `all_targets'.
make[2]: Leaving directory
`/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/crypto'
make[1]: Leaving directory
`/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/crypto'
make CFLAGS="-D__KERNEL__
-I/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-fno-unit-at-a-time " -C  arch/xen/kernel
make[1]: Entering directory
`/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/arch/xen/kernel'
gcc -D__KERNEL__
-I/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-fno-unit-at-a-time   -nostdinc -iwithprefix include
-DKBUILD_BASENAME=process  -c -o process.o process.c
process.c:46:27: asm/multicall.h: No such file or directory
process.c: In function `cpu_idle':
process.c:104: warning: implicit declaration of function
`HYPERVISOR_block'
process.c:110: warning: implicit declaration of function
`HYPERVISOR_yield'
process.c: In function `copy_thread':
process.c:237: error: structure has no member named `io_pl'
process.c: In function `__switch_to':
process.c:322: warning: implicit declaration of function
`MULTICALL_flush_page_update_queue'
process.c:337: warning: implicit declaration of function
`queue_multicall0'
process.c:340: warning: implicit declaration of function
`queue_multicall2'
process.c:341: error: `xen_start_info' undeclared (first use in this
function)
process.c:341: error: (Each undeclared identifier is reported only once
process.c:341: error: for each function it appears in.)
process.c:346: error: structure has no member named `io_pl'
process.c:348: warning: implicit declaration of function
`queue_multicall1'
process.c:352: warning: implicit declaration of function
`execute_multicall_list'
process.c:366: warning: implicit declaration of function
`HYPERVISOR_set_debugreg'
make[1]: *** [process.o] Error 1
make[1]: Leaving directory
`/download/kernels/xen-2.0/linux-2.4.30-xenUOSW/arch/xen/kernel'
make: *** [_dir_arch/xen/kernel] Error 2


By the other hand, trying to compile the 2.4 xenU kernel a was unable to
put to work some rules in iptables related to NETMAP, multiport,
iprange.

I don't know. I see that I don't need apply a patch because I'll use
iptables 1.3.3 that have this functionality but the rules does not work.

Someone can give some help or point to the right path?

Best regards,


-- 
Jorge Isaac Davila Lopez


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] xen 2.0.7 / gcc 3.4 / iptables 1.3.3, Jorge I. Davila L. <=