Problem with building L4Linux

Nuno Santos nuno.santos at mpi-sws.org
Tue Dec 7 09:24:52 CET 2010


Hi

I'm having trouble with building l4linux. First, I had the same problem 
as reported in this [1] post; then I tried to build l4linux from the 
latest snapshot as suggested in [2] by following the steps in the readme 
file ('make setup' and 'make').

If I setup the target as x86-32, at some point the build process fails 
with the following output (without further description of the error):

"
make[6]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind/build'
make[5]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg/valgrind'
make[4]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
make[3]: *** [pkg] Error 2
make[3]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
make[2]: *** [x] Error 2
make[2]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/x86'
Error building the L4Re 'obj/l4/x86' variant.
"

If I setup to the amd64 target, the build process fails with a 
compilation error:

"
/tmp/camlasm564f4e.s: Assembler messages:
/tmp/camlasm564f4e.s:580: Error: junk `lazy_force(%rip)' after expression
/tmp/camlasm564f4e.s:580: Error: suffix or operands invalid for `lea'
/tmp/camlasm564f4e.s:785: Error: junk `lazy_force(%rip)' after expression
/tmp/camlasm564f4e.s:785: Error: suffix or operands invalid for `lea'
Assembler error, input left in file /tmp/camlasm564f4e.s
make[8]: *** [stream.cmx] Error 2
...
make[4]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4/pkg'
make[3]: *** [pkg] Error 2
make[3]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/src/l4'
make[2]: *** [x] Error 2
make[2]: Leaving directory 
`/local/l4re-snap/l4re-snapshot-2010111519/obj/l4/amd64'
Error building the L4Re 'obj/l4/amd64' variant.
"

The problematic assembly instruction is:
leaq    $25lazy_force(%rip), %rax

I'm using the snapshot from Nov 15th, on a machine running linux 2.6.32, 
gcc 4.3.2.

Any ideas on how to fix it?

Thanks for your help!
--Nuno

[1] 
http://www.mail-archive.com/l4-hackers@os.inf.tu-dresden.de/msg04380.html
[2] 
http://www.mail-archive.com/l4-hackers@os.inf.tu-dresden.de/msg04383.html




More information about the l4-hackers mailing list