hi all, last time I put a error message to the l4-hacker ,and you send me a mail that ?I have cut away the first error.So I send the full infomations to you when I compiled it.By useing the cpu info,when I compile fiasco I do this:
|| Architecture (AMD64 processor family) ---> || Platform (PC platform) ---> || CPU (AMD Opteron / Athlon64) ---> || for scheduling) ---> || [*] Enables workaroud for AMD FPU security leak
It sames that fiasco OK,but when I compile l4 with the following info:
(x86) Target Architecture CPU type: "586" (L4.Fiasco) ABI
errors comes out like this:
... Generating generic_ts-server.c CC="gcc -m32" /home/l4/tudos/l4/../dice/src/dice --require="3.2.0" -P-DUSE_UCLIBC=y -P-DRAM_BASE=0x0 -P-DSYSTEM_x86_l4v2 -P-DARCH_x86 -P-DCPUTYPE_586 -P-DL4API_l4v2 -P-DCONFIG_L4_CALL_SYSCALLS -P-DCONFIG_L4_ABS_SYSCALLS -P-I/home/l4/tudos/build/include/x86/l4v2 -P-I/home/l4/tudos/build/include/l4v2 -P-I/home/l4/tudos/build/include/x86 -P-I/home/l4/tudos/build/include -P-I/home/l4/tudos/l4/../dice/include -P-I/home/drops/include/x86/l4v2 -P-I/home/drops/include/l4v2 -P-I/home/drops/include/x86 -P-I/home/drops/include -P-nostdinc -P-I/home/l4/tudos/build/include/x86/uclibc -P-I/home/l4/tudos/build/include/uclibc -P-I/home/l4/tudos/build/include/uclibc++ -P-I/home/drops/include/x86/uclibc -P-I/home/drops/include/uclibc -P-I/home/drops/include/uclibc++ -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include-fixed -Bifiasco -Bpia32 -MD /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl In file included from /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl:0, from l4/sys/types.h:1: /home/l4/tudos/build/include/x86/l4v2/l4/sys/types.h:398.20-29: error: value is out of range make[4]: *** [generic_ts-server.c] error 1 make[4]: Leaving directory `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-x86-l4v2' make[3]: *** [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-x86-l4v2] error 2 make[3]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts/idl' make[2]: *** [idl] error 2 make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' make[1]: *** [generic_ts.headers] error 2 make[1]: Leaving directory `/home/l4/tudos/l4/pkg' make: *** [pkg] error 2 -----------------------------------------------------------------------
firstly I think maybe I didn't do the right selecet,then I change it:
(amd64) TargetArchitecture CPU type: "k7" (L4.Fiasco)
but there is another errors:
... Generating generic_ts-server.c CC="gcc -m64" /home/l4/tudos/l4/../dice/src/dice --require="3.2.0" -P-DUSE_UCLIBC=y -P-DRAM_BASE=0x0 -P-DSYSTEM_amd64_l4v2 -P-DARCH_amd64 -P-DCPUTYPE_k7 -P-DL4API_l4v2 -P-DCONFIG_L4_CALL_SYSCALLS -P-DCONFIG_L4_ABS_SYSCALLS -P-I/home/l4/tudos/build/include/amd64/l4v2 -P-I/home/l4/tudos/build/include/l4v2 -P-I/home/l4/tudos/build/include/amd64 -P-I/home/l4/tudos/build/include -P-I/home/l4/tudos/l4/../dice/include -P-I/home/drops/include/amd64/l4v2 -P-I/home/drops/include/l4v2 -P-I/home/drops/include/amd64 -P-I/home/drops/include -P-nostdinc -P-I/home/l4/tudos/build/include/amd64/uclibc -P-I/home/l4/tudos/build/include/uclibc -P-I/home/l4/tudos/build/include/uclibc++ -P-I/home/drops/include/amd64/uclibc -P-I/home/drops/include/uclibc -P-I/home/drops/include/uclibc++ -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include-fixed -Bifiasco -Bpamd64 -MD /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl In file included from /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl:0, from l4/sys/types.h:1, from /home/l4/tudos/build/include/amd64/l4v2/l4/sys/types.h:185: /home/l4/tudos/build/include/l4/sys/__l4_fpage-64bit.h:96.55-65: error: value is out of range make[4]: *** [generic_ts-server.c] error 1 make[4]: Leaving directory `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2' make[3]: *** [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2] error 2 make[3]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts/idl' make[2]: *** [idl] error 2 make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' make[1]: *** [generic_ts.headers] error 2 make[1]: Leaving directory `/home/l4/tudos/l4/pkg' make: *** [pkg] error 2
I think It can work on AMD64,could you help me?thank you very much!
fangzhsh,
Hi,
On Mon Apr 07, 2008 at 19:15:03 +0800, l4 wrote:
hi all, last time I put a error message to the l4-hacker ,and you send me a mail that ?I have cut away the first error.So I send the full infomations to you when I compiled it.By useing the cpu info,when I compile fiasco I do this:
|| Architecture (AMD64 processor family) ---> || Platform (PC platform) ---> || CPU (AMD Opteron / Athlon64) ---> || for scheduling) ---> || [*] Enables workaroud for AMD FPU security leak
You are compiling Fiasco for AMD64 and L4Env for x86 (IA32). That will not work together. Please also compile Fiasco for 32bit.
It sames that fiasco OK,but when I compile l4 with the following info:
(x86) Target Architecture CPU type: "586" (L4.Fiasco) ABI
errors comes out like this:
In file included from /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl:0, from l4/sys/types.h:1: /home/l4/tudos/build/include/x86/l4v2/l4/sys/types.h:398.20-29: error: value is out of range
This has been fixed in dice, please update your source and rebuild.
I think It can work on AMD64,could you help me?thank you very much!
Note that only a subset works on amd64 compared to ia32. I thus recommend using ia32.
Adam
I think It can work on AMD64,could you help me?thank you very much!
Note that only a subset works on amd64 compared to ia32. I thus recommend using ia32.
I think if we have a pure 64-bit machine but we indeed to run fiasco with full features, as Adam suggested to use ia32 , qemu is good choice. we could use qemu to emulate a pure 32-bit environment for the Fiasco/32-bit. Right? Thanks. Cheng
On Tue Apr 08, 2008 at 20:40:07 +0200, cheng.guanghui.ml wrote:
I think It can work on AMD64,could you help me?thank you very much!
Note that only a subset works on amd64 compared to ia32. I thus recommend using ia32.
I think if we have a pure 64-bit machine but we indeed to run fiasco with full features, as Adam suggested to use ia32 , qemu is good choice. we could use qemu to emulate a pure 32-bit environment for the Fiasco/32-bit. Right?
Any amd64 machine can run normal ia32 code, not just 64bit code. But using qemu for trying things out is probably a good idea anyway.
Adam
l4-hackers@os.inf.tu-dresden.de