While building xen itself: ld -melf_i386 -T xen.lds -N \ boot/x86_32.o /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/built_in.o /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/drivers/built_in.o /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o \ /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/symbols-dummy.o -o /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/.xen-syms.0 /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/built_in.o: In function `strstr'': /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/string.c:431: undefined reference to `memcmp'' /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o: In function `emulate_forced_invalid_op'': /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/traps.c:563: undefined reference to `memcmp'' /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/traps.c:573: undefined reference to `memcmp'' /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o: In function `do_invalid_op'': /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/traps.c:629: undefined reference to `memcmp'' /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o: In function `dmi_iterate'': /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/dmi_scan.c:120: undefined reference to `memcmp'' /home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o:/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/mpparse.c:383: more undefined references to `memcmp'' follow This is happening on mandriva cooker 32 bits, with gcc-4.2.1 and glibc 2.6 and 2.6.21 kernel headers. -- Guillaume Rousse Moyens Informatiques - INRIA Futurs Tel: 01 69 35 69 62 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
At 22:42 19/07/2007, Guillaume Rousse wrote:>While building xen itself: > >ld -melf_i386 -T xen.lds -N \ > boot/x86_32.o >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/built_in.o >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/drivers/built_in.o >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o >\ > >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/symbols-dummy.o >-o >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/.xen-syms.0 >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/built_in.o: >In function `strstr'': >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/common/string.c:431: >undefined reference to `memcmp'' >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o: >In function `emulate_forced_invalid_op'': >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/traps.c:563: >undefined reference to `memcmp'' >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/traps.c:573: >undefined reference to `memcmp'' >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o: >In function `do_invalid_op'': >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/traps.c:629: >undefined reference to `memcmp'' >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o: >In function `dmi_iterate'': >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/dmi_scan.c:120: >undefined reference to `memcmp'' >/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/built_in.o:/home/guillomovitch/cooker/xen-uptodate/BUILD/xen-3.1.0-src/xen/arch/x86/mpparse.c:383: >more undefined references to `memcmp'' follow > >This is happening on mandriva cooker 32 bits, with gcc-4.2.1 and glibc >2.6 and 2.6.21 kernel headers.I suspect this is more to do with the compiler than Xen. Have you successfully compiled any other version of Xen? I know that gcc-4.1.1 works OK for 3.1.0. -- Mats>-- >Guillaume Rousse >Moyens Informatiques - INRIA Futurs >Tel: 01 69 35 69 62 > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 19/7/07 22:42, "Guillaume Rousse" <Guillaume.Rousse@inria.fr> wrote:> This is happening on mandriva cooker 32 bits, with gcc-4.2.1 and glibc > 2.6 and 2.6.21 kernel headers.Where do these Xen bits come from? If you ''hg clone http://xenbits.xensource.com/xen-unstable.hg'' and ''make xen'' inside the resulting directory, do you get the same problem? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Guillaume Rousse
2007-Jul-20 09:20 UTC
Re: [Xen-devel] compilation trouble with latest xen
Keir Fraser a écrit :> On 19/7/07 22:42, "Guillaume Rousse" <Guillaume.Rousse@inria.fr> wrote: > >> This is happening on mandriva cooker 32 bits, with gcc-4.2.1 and glibc >> 2.6 and 2.6.21 kernel headers. > > Where do these Xen bits come from? >From 3.1 source tarball.>If you ''hg clone > http://xenbits.xensource.com/xen-unstable.hg'' and ''make xen'' inside the > resulting directory, do you get the same problem?Actually, the pb doesn''t comes from xen itself, but from rpm building procedure (parallel build and specific optflags): building manually xen doesn''t trigger the error. So I doubt using unstable version would help. -- Guillaume Rousse Moyens Informatiques - INRIA Futurs Tel: 01 69 35 69 62 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 20/7/07 10:20, "Guillaume Rousse" <Guillaume.Rousse@inria.fr> wrote:>> If you ''hg clone >> http://xenbits.xensource.com/xen-unstable.hg'' and ''make xen'' inside the >> resulting directory, do you get the same problem? > Actually, the pb doesn''t comes from xen itself, but from rpm building > procedure (parallel build and specific optflags): building manually xen > doesn''t trigger the error. So I doubt using unstable version would help.There are two lines in xen/include/asm-x86/string.h relating to memcmp and __HAVE_ARCH_MEMCP. If you comment them out then your build will probably work. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel