l4-hackers

l4-hackers@os.inf.tu-dresden.de

2827 discussions

Error in building l4linux-2.6-env
by Wang, Chip 12 Jul '05

12 Jul '05

Hi, After skipped building fprov-l4 and kill-l4 in l4/pkg/loader/examples, I managed to get a little further. This time my make failed at l4/pkg/dde for conflicting function prototypes. It appears the make was using Linux 2.4 header files while building for 2.6 Does anybody have an idea of what went wrong? Chip make[5]: Entering directory `/home/drops/l4/pkg/dde_linux/lib/src/OBJ-x86_586-l4v2' ... Compiling mm.o LD_PRELOAD=/home/drops/l4/tool/gendep/libgendep.so GENDEP_TARGET=mm.o GENDEP_BINARY=cc1 gcc -c -D__KERNEL__ -DDDE_LINUX -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../lib/include -I../../../../../include/x86/l4/dde_linux -I/home/drops/include/x86/l4/dde_linux -I../../../../../include/linux-24 -I/home/drops/include/linux-24 -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/home/drops/include/x86/l4v2 -I../../../../../include/l4v2 -I/home/drops/include/l4v2 -I../../../../../include/x86 -I/home/drops/include/x86 -I../../../../../include -I/home/drops/include -nostdinc -DOSKIT -I../../../../../../oskit10 -I../../../../../../oskit10/oskit/c -I/home/drops/include/oskit10 -I/home/drops/include/oskit10/oskit/c -I/usr/lib/gcc/i586-mandrake-linux-gnu/3.4.3/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -fno-strict-aliasing /home/drops/l4/pkg/dde_linux/lib/src/mm.c -o mm.o In file included from ../../../../../include/linux-24/linux/bitops.h:69, from ../../../../../include/x86/l4/dde_linux/asm/system.h:10, from ../../../../../include/x86/l4/dde_linux/linux/spinlock.h:8, from ../../../../../include/linux-24/linux/wait.h:16, from ../../../../../include/linux-24/linux/fs.h:12, from ../../../../../include/linux-24/linux/capability.h:17, from ../../../../../include/linux-24/linux/binfmts.h:5, from ../../../../../include/x86/l4/dde_linux/linux/sched.h:11, from ../../../../../include/linux-24/linux/mm.h:4, from ../../../../../include/linux-24/linux/slab.h:14, from /home/drops/l4/pkg/dde_linux/lib/src/mm.c:50: ../../../../../include/linux-24/asm/bitops.h:343: warning: static declaration of 'ffs' follows non-static declaration In file included from ../../../../../include/x86/l4/dde_linux/linux/sched.h:25, from ../../../../../include/linux-24/linux/mm.h:4, from ../../../../../include/linux-24/linux/slab.h:14, from /home/drops/l4/pkg/dde_linux/lib/src/mm.c:50: ../../../../../include/linux-24/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule' ../../../../../include/x86/l4/dde_linux/asm/smp.h:44: error: previous declaration of 'smp_send_reschedule' was here ../../../../../include/linux-24/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule' ../../../../../include/x86/l4/dde_linux/asm/smp.h:44: error: previous declaration of 'smp_send_reschedule' was here make[5]: *** [mm.o] Error 1 make[5]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib/src/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib' make[2]: *** [lib] Error 2 make[2]: Leaving directory `/home/drops/l4/pkg/dde_linux' make[1]: *** [dde_linux.lib] Error 2 make[1]: Leaving directory `/home/drops/l4/pkg' make: *** [pkg] Error 2 The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

L4Env Isolating Hard Drives
by Julian Grizzard 12 Jul '05

12 Jul '05

All, Consider a x86 computer that has two physical IDE hard drives. Is it possible for an L4Env I/O manager to allocate exactly one hard drive to an L4Linux2.6 server and allocate the second hard drive to another L4 task in a way that the L4Linux2.6 server has no way of knowing that the second hard drive exists? Thanks! -Julian

3 3

Help! Unable to build L4Env-0.2
by Wang, Chip 12 Jul '05

12 Jul '05

Hi fellow hackers, I am a newbie here. I am trying to build my first L4Linux-2.6 setup, but failed at building L4Env. I downloaded and unpacked the following S/W from the L4Env download page: - l4env-0.2 tarball - dde-0.2 tarball - libstdc++.0.2 - oskit-06302003 - oskit10-06302003 I also checked out L4Linux-2.6-env from CVS. I then followed the instructions and did 'make config' and 'make' from inside the 'l4' directory. The compilation eventually failed at building l4/pkg/loader. The linker complained that the library -lcon was missing. My Linux is 2.6.11 from Mandrake with KDE. My platform is an Acer TravelMate c300 notebook. I searched the mailing list archive but didn't see similar report of the problem I figure I must be missing some other pieces or having the wrong versions. By the way, I also got errors when building 'multiboot-smp'. I followed the suggestion to skip the example by creating a null executable. Should I do the same for this example? Could someone please show me what I did wrong? Thanks in advance for your help Chip The last portion of the build log is attached below. === Building servers, examples of "loader" === PWD=/home/drops/l4/pkg/loader make -C loader all -o lib -o include -o idl make[2]: Entering directory `/home/drops/l4/pkg/loader' test -f server/broken -o -f server/obsolete || \ if [ -f server/Makefile ] ; then PWD=/home/drops/l4/pkg/loader/server make -C server ; fi make[3]: Entering directory `/home/drops/l4/pkg/loader/server' test -f src/broken -o -f src/obsolete || \ if [ -f src/Makefile ] ; then PWD=/home/drops/l4/pkg/loader/server/src make -C src ; fi make[4]: Entering directory `/home/drops/l4/pkg/loader/server/src' PWD=/home/drops/l4/pkg/loader/server/src/OBJ-x86_586-l4v2 make -C OBJ-x86_586-l4v2 -f Makefile make[5]: Entering directory `/home/drops/l4/pkg/loader/server/src/OBJ-x86_586-l4v2' ==> Linking loader LD_PRELOAD=/home/drops/l4/tool/gendep/libgendep.so GENDEP_TARGET=loader GENDEP_BINARY=ld gcc -o loader ../../../../../lib/x86_586/crt0.o trampoline.s.o main.o cfg-parse.o cfg.o pager.o app.o fprov-if.o dm-if.o exec-if.o idl.o events.o lib.o loader-server.o -Ttext=0x01300000 -L../../../../../lib/x86_586/l4v2 -L/home/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/home/drops/lib/x86_586 -L../../../../../lib -L/home/drops/lib -L../../../../../../oskit10/lib -L/home/drops/lib/oskit10 -T../../../../../lib/x86_586/main_stat.ld -ll4exec -lgeneric_ts -lgeneric_fprov -lloaderif -lcon -ldm_phys -levents -lparsecmdline -static -loskit10_support_l4env.o -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver -lnames -ll4util -lrmgr -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -loskit_c -loskit_kern -loskit_clientos -loskit_lmm -loskit_kern -loskit_c /usr/lib/gcc/i586-mandrake-linux-gnu/3.4.3/libgcc.a -loskit_c -Ttext=0x01300000 -Wl,-gc-sections /usr/bin/ld: cannot find -lcon collect2: ld returned 1 exit status make[5]: *** [loader] Error 1 make[5]: Leaving directory `/home/drops/l4/pkg/loader/server/src/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/drops/l4/pkg/loader/server/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/drops/l4/pkg/loader/server' make[2]: *** [server] Error 2 make[2]: Leaving directory `/home/drops/l4/pkg/loader' make[1]: *** [loader.bin] Error 2 make[1]: Leaving directory `/home/drops/l4/pkg' make: *** [pkg] Error 2 The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

build failure and fix for typo
by Julian Stecklina 12 Jul '05

12 Jul '05

Hello, I tried to build fiasco on FreeBSD today using the following commands: > cd kernel/fiasco > gmake config > env AWKP=awk gmake I got as far as: gmake srcdir=/usr/home/blitz/src/os/l4/kernel/fiasco/src -f /usr/home/ blitz/src/os/l4/kernel/fiasco/src/Makefile.sub2 all gmake[3]: Entering directory `/usr/home/blitz/src/os/l4/kernel/fiasco/build' ... Making kip.o g++ -c -MD -nostdinc -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/types/ia32 -I/usr/home/blitz/src/os/l4/kernel/fiasco/src/types -I/ usr/home/blitz/src/os/l4/kernel/fiasco/src/drivers/ia32 -I/usr/home/ blitz/src/os/l4/kernel/fiasco/src/drivers -I/usr/home/blitz/src/os/l4/ kernel/fiasco/src/kern/ia32 -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/kern/shared -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/kern -I/ usr/home/blitz/src/os/l4/kernel/fiasco/src/boot -I/usr/home/blitz/src/ os/l4/kernel/fiasco/src/lib/libk/ia32 -I/usr/home/b litz/src/os/l4/ kernel/fiasco/src/lib/libk -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/lib/kern/include -I/usr/home/blitz/src/os/l4/ kernel/fiasco/src/lib/ amm -I/usr/home/blitz/src/os/l4/kernel/fiasco/src/lib/gzip -I/usr/home/ blitz/src/os/l4/kernel/fiasco/src/lib/di sasm -I/usr/home/blitz/src/os/ l4/kernel/fiasco/src/lib/perfctr -I/usr/home/blitz/src/os/l4/kernel/ fiasco/src/lib/regex -I/usr/home/bl itz/src/os/l4/kernel/fiasco/src/lib/ minilibc/ia32/include -I/usr/home/blitz/src/os/l4/kernel/fiasco/src/lib/ minilibc/include -I. -Iauto -I/usr/lib//include -fno-implement-inlines -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium2 -fno-defer-pop -freg-struct-re turn -g -Wall -W -Wformat=2 -ffunction-sections -fomit- frame-pointer -gstabs+ -fno-rtti -fno-exceptions -Wno-non-virtual- dtor -O2 - finline-limit=10000 --param large-function-insns=10000 - fweb -frename-registers auto/kip.cc -o kip.o In file included from auto/ kip.h:6, from auto/kip.cc:3: /usr/home/blitz/src/os/l4/kernel/fiasco/ src/types/types.h:4:20: stddef.h: No such file or directory (some spaces have crept in due to copy&paste from xterm) minilibc does not seem to provide stddef.h, so the one of the host compiler is probably meant (is this correct?), but -I/usr/include//bin seems kind of bogus. Has anyone an idea where to tweak this? As a general remark: Hardcoded paths in the build process should be avoided. Best example #!/bin/bash in scripts which should be replaced by #!/usr/bin/env bash or even better #!/bin/sh for better portability. I think the whole build process needs some kind of autoconf magic, too, to make it less GNU/Linux dependent. Regards, -- Julian Stecklina LISP has survived for 21 years because it is an approximate local optimum in the space of programming languages. - John McCarthy (1980)

2 7

using l4linux structures in l4
by Andrew Davenport 11 Jul '05

11 Jul '05

Hello, What is the simplest way to use (eg) the task_struct from linux inside the l4 microkernel. I want to use exactly the same declaration in the kernel, but I am having difficulty using it. Thanks, Andrew

2 1

exception -> l4_ipc ?
by Andrew Davenport 11 Jul '05

11 Jul '05

hi, i see thread::raise_exception(ts), and i know this is where l4 notices a linux sys call (int 0x80), however, i do *not* see where the ipc is sent to the linux server to tell it that a syscall has occured (and to get the parameters and handle it)... thanks in advance, -andrew

2 7

documentation booting fiasco
by Emanuel Thomas 11 Jul '05

11 Jul '05

Hello, is there any detailed documentation about the Fiasco boot process available? Emanuel

3 2

getting older version of l4linux 2.6
by fabs0028＠free.fr 07 Jul '05

07 Jul '05

Hello i would like to get l4linux 2.6.9 to compare with my current fedora kernel. Is it possible to get it with cvs ? I searched but i didn't find a way. Thanx for the help Fabien Chaillou

4 4

l4v2: l4linux2.6 Syscall logging via IPC in l4
by Andrew Davenport 07 Jul '05

07 Jul '05

Hello, I am trying to log linux syscalls from l4linux2.6 on top of l4v2. What is the simplest way to log this at the IPC level (i have enabled exception IPC) and log all the parameters? Thanks, Andrew

3 3

Some questions
by fabs0028＠free.fr 07 Jul '05

07 Jul '05

Hello, I first wanted to signal about a little problem i found : when i launch an application i did for l4 with the loader it works fine but after its end i want to launch a legacy linux application and i get the message KERNEL: Security violation: Not pager of 36. Maybe i forgot something to close my program but i don't know what or maybe it is something else. I also wondered if it was possible to build a standard linux kernel from the l4linux sources ? I think so but i'm not sure. And for a last question i'd like to know if there's a way to share devices such as for example hard drives between l4 and the l4linux server. I saw dde but i don't know if it is still up with the 2.6 portage and i haven't found a lot of doc about it except the manual. Thanx a lot for your help. Fabien Chaillou

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers