Hi,all
I have compiled l4 on my machine, my cpu type is amd64, when I compiled l4, I got errors as below. In my config file I chose the  cpu type as amd64 and kept the other things not changed.  Then I used the command
       make O=/home/licy/Desktop/trunk/build CC="gcc -disable-multilib" to compile. And I got the errors:

/home/licy/Desktop/trunk/build/include/linux-24/linux/string.h:78: warning: conflicting types for built-in function '__builtin_memcmp'
/tmp/cc6FM9DF.s: Assembler messages:
/tmp/cc6FM9DF.s:2683: Error: suffix or operands invalid for `mov'
/tmp/cc6FM9DF.s:2684: Error: Incorrect register `%rax' used with `l' suffix
/tmp/cc6FM9DF.s:5510: Error: suffix or operands invalid for `and'
/tmp/cc6FM9DF.s:7122: Error: suffix or operands invalid for `and'
/tmp/cc6FM9DF.s:7201: Error: Incorrect register `%rax' used with `l' suffix

Indeed I found http://lists.okl4.org/pipermail/developer/2007-April/000038.html who got the similar errors and at last the one gave an advice to simulate in qemu. Someone said that now we can compile l4 on amd64 machines, and I want to know what my problem is. My gcc version is

Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --disable-libmudflap --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.2.3 (Debian 4.2.3-3)

licy@licy:~/Desktop/trunk/l4$ ld -v
GNU ld (GNU Binutils for Debian) 2.18.0.20080103

Whether it's the compiler's problem or we still can't compile l4 on amd64 machines, I hope someone give me some help and thanks a lot. Someone said that I shouldn't use the ia32 headers and just use the amd-64 headers is OK, but I still don't get the results, maybe there are patches for this problem or my compiling way is incorrect, just tell me and i'll have a try.


Eh, I got the newest version of the trunk, I forgot telling you this.