l4-hackers July 2008

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

8 participants
10 discussions

Back to UTCB IPC
by Marc CHALAND 11 Oct '09

11 Oct '09

Hi, I am back with my problem with UTCB IPC. To sum up the context : I use pure l4env applications. Here is the scenario between my server and my client : 1. client makes an UTCB IPC to manager. Manager does an l4rm_area_reserve, creates a rcv_fpage, creates worker and sends back worker thread id to client. 2. client allocates memory and associated flexpage and sends it to server. 3. UTCB IPC is sent to worker with 3 parameters : - on client side : utcb->values=0xbff00200: arg1=0x2 arg2=0x1 arg3=0x6 - on server side : utcb->values=0xbff00200: arg1=0x241401 arg2=0x0 arg3=0x7069776c It seems that 0xbff00200 is not mapped on the same memory on client and server side. As there is no problem for first IPC (utcb->values is also 0xbff00200), is there any potential problem with flexpage ? As utcb->values is still the same, what happens if several threads try to make UTCB IPC ? Another question : when I link my application with liblogserver.a, I have strange logs : .rm.sem.mainMain function returned. It seems that .rm .sem and .main are added by l4env, but I didn't find where. Regards Marc

4 9

DirectFB
by Saya Sheng (盛淑蕙) 31 Jul '08

31 Jul '08

Hi,all I've been obsessed by some questions about window system recently. It is known that we can use dope API to create graphic user interface but it seems insufficient to me, and therefore i am wondering whether or not DirectFB can be used as a window system such that a widget toolkit can provide abundant resource. As for a application in X window system, does it need to spend much time to boot if X window system is run on DROPS through nitpicker without running l4linux? any advice is welcomed. thanks in advance. best regards Saya

1 0

l4linux booting problem
by fei li 24 Jul '08

24 Jul '08

Hi,all I have compiled l4linux and tried to boot it in qemu environment. My hardware environment is CPU: Celeron D 2.53G，512M memor. Next is my menu.lst title L4Linux kernel /bootstrap -serial -modaddr 0x2000000 module /fiasco -serial_esc -comport 1 module /sigma0 module /roottask task modname "bmodfs" attached 5 modules module /names module /l4io module /events module /dm_phys module /simple_ts module /rtc module /con --vbemode 0x117 module /bmodfs module /vmlinuz module /l4linux.cfg module /libloader.s.so module /libld-l4.s.so module /drops-rd.rd module /loader --fprov=BMODFS l4linux.cfg In l4linux.cfg, I wrote sleep 1 task "vmlinuz" "mem=64M load_ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=drops-rd.rd" all_sects_writable allow_cli allow_vga and I use qemu -serial stdio -m 200 -cdrom image.iso to boot, at fisrt it told me qemu didn't have enough main memory, so I assigned 200M, then I got the errors below *simplets| Configured for 64 tasks. *rtc | Date:21.07.2008 Time:13:55:24 *bmodfs | Passed the following modules: *bmodfs | module "/vmlinuz" (3143kB) *bmodfs | module "/l4linux.cfg" (1kB) *bmodfs | module "/libloader.s.so" (636kB) *bmodfs | module "/libld-l4.s.so" (484kB) *bmodfs | module "/drops-rd.rd" (16384kB) *io | Using platform configuration 'x86' *io | PCI: Using configuration type 1 *io | PCI: Probing PCI hardware *io | PCI: Probing PCI hardware (bus 00) *io | PCI: PIIX3: Enabling Passive Release on 00:01.0 *io | Limiting direct PCI/PCI transfers. *io | Activating ISA DMA hang workarounds. *io | 00000000-ffffffff : PCI mem *io | e0000000-e1ffffff : Cirrus Logic GD 5446 *io | e2000000-e2000fff : Cirrus Logic GD 5446 *io | 0000-ffff : PCI IO *io | 0cf8-0cff : PCI conf1 *io | 1000-100f : Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] *io | 1400-14ff : Realtek Semiconductor Co., Ltd. RTL-8029(AS) *io | b100-b11f : Intel Corporation 82371AB/EB/MB PIIX4 ACPI *con | Using fast memcpy. *io | Available IRQs=[ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f 10 11 ] *con | Character size is 8x14, font has 256 characters *con | Trying execution of ``set VBE mode'' using x86emu *con | Found VESA BIOS version 2.0 *con | OEM VGABIOS Cirrus extension *con | VBE mode 0x117 successfully set. *con | VESA reports 1024x768@16 2048bpl (00bb) [4096kB] *con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 *con | No supported accelerated graphics card detected *con | Mapped I/O video mem e0000000 => 00400000 [4096kB] via l4io *con | Using MMXEXT for colorspace transform *con | L4INPUT native mode activated *con | L4INPUT: !!! W A R N I N G !!! *con | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. *con | L4INPUT: !!! W A R N I N G !!! *con | L4INPUT: Registered 0xb03d90 for callbacks. ROOT: Sending ports 0060-006f to task #06 *con | serio: i8042 AUX port at 0x60,0x64 irq 12 *con | serio: i8042 KBD port at 0x60,0x64 irq 1 *con | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 *con | input: AT Translated Set 2 keyboard on isa0060/serio0 *con | input: PC Speaker *con | input: L4 input event injector *con | L4 input event injector: IRQ handler up *con | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 *con | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 *con | connect "PC Speaker", isa0061/input0 *con | connect "L4 input event injector", l4/sys *con | Running as B.02. Video mode is 1024x768@16. *loader | sleeping for 1000 ms *loader | vmlinuz: Starting application using libld-l4.s.so *loader | vmlinuz,#e: Loading binary *loader | vmlinuz,#e: Loading ldso *loader | vmlinuz,#e: Starting libld-l4.s.so at 000138b0 via 0000cf3c *l4lx | ======> L4Linux 2.6 starting... <======== *l4lx | Linux version 2.6.23-l4 (licy@licy) (gcc version 4.1.3 20070929 (prer *l4lx : elease) (Ubuntu 4.1.2-16ubuntu2)) #1 Mon Jul 21 16:23:26 CST 2008 *l4lx | Binary name: vmlinuz *l4lx | Kernel command line (5 args): mem=64M load_ramdisk=1 ramdisk_size=163 *l4lx : 84 root=/dev/ram l4env_rd=drops-rd.rd *l4lx | Image: 00400000 - 007b4000 [3792 KiB]. *l4lx | Areas: Text: 00400000 - 006b4000 [2768kB] (a bit longer) *l4lx | Data: 006b4000 - 006d307c [124kB] *l4lx | Initdata: 006d6000 - 00710000 [232kB] *l4lx | BSS: 00712000 - 007b1080 [636kB] *l4lx | l4lx_thread_create: Created thread 0e.03 (tamer0) *l4lx | Tamer0 is 0e.03 *l4lx | Using tamed mode. *l4lx | Connecting to l4io server. *l4lx | l4env_linux_startup thread 4. *l4lx | l4lx_thread_create: Created thread 0e.04 (cpu0) *l4lx | main thread will be 0e.04 *l4lx | l4env_register_pointer_section: addr = 00400000 size = 3215360 *l4lx | sec-w-init: virt: 0x00400000 to 0x00710fff [3140 KiB] *l4lx | Noncontiguous region for sec-w-init *l4lx | sec-w-init: Number of physical regions: 5, 3215360 Bytes *l4lx | sec-w-init: 1: Phys: 0x0108a000 to 0x010ea000, Size: 393216 *l4lx | sec-w-init: 2: Phys: 0x012f2000 to 0x01300000, Size: 57344 *l4lx | sec-w-init: 3: Phys: 0x001aa000 to 0x002ad000, Size: 1060864 *l4lx | sec-w-init: 4: Phys: 0x01419000 to 0x01500000, Size: 946176 *l4lx | sec-w-init: 5: Phys: 0x01347000 to 0x01400000, Size: 757760 *l4lx | main thread: received startup message. *l4lx | Main thread running, waiting... *l4lx | setup_l4env_memory: Forcing superpages for main memory *l4lx | Main memory size: 64MB *l4lx | Main memory: virt: 0x00800000 to 0x047fffff [65536 KiB] *l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes *l4lx | Main memory: 1: Phys: 0x03c00000 to 0x07c00000, Size: 67108864 *l4lx | Filling lower ptabs... *l4lx | Done (1032 entries). *l4lx | l4env_register_pointer_section: addr = 00712000 size = 663552 *l4lx | end: virt: 0x00712000 to 0x007b3fff [648 KiB] *l4lx | end: Number of physical regions: 1, 663552 Bytes *l4lx | end: 1: Phys: 0x01250000 to 0x012f2000, Size: 663552 *l4lx | l4env_rd_path: drops-rd.rd *l4lx | Loading: drops-rd.rd *l4lx | INITRD: Size of RAMdisk is 16384KiB *l4lx | RAMdisk from 04800000 to 05800000 [16384KiB] *l4lx | l4lx_thread_create: Created thread 0e.05 (timer.i0) *l4lx | Jumping over 4x 'hlt' at 0x6df7e0 *l4lx | L4RM: [PF] read at 0x00000000, ip 00000000, src E.02 *l4lx | [E.0] l4rm/lib/src/pagefault.c:81:__unknown_pf(): *l4lx | unhandled page fault --PANIC, 'g' for exit------------------------------------IP: a00b3754 [l4lx.rm] (e.00) jdb: At last lines you will see the problem, and I checked the fiasco, it was ok. I found someone had similar problems but not the same, and Adam said L4Linux is not allowed to do port accesses (except it is explicitely allowed). I don't know what my problem is and I hope someone will give me some advice and thanks a lot.

3 6

Re: DDE library
by Björn Döbel 21 Jul '08

21 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, > Hi, Bjoern please use the mailing list. It might give others the opportunity to answer _and_ it might help other people with similar problems to get their work done. :) > Thanks for your reply. I rebuilt dde package and got the library > 'libdde_linux26_sound.a' after downloading sound,c from Linux > 2.6.20.19, but now i have a another question, some sound driver source > files from linux 2.6.20.19/sound/pci/hda were copied to my sound > package directory and do i need to combine these files with main.c > including initialization rountine to generate a sound server? if yes, > how to do that? I've tried to compile these sound driver as a library, > but unfortunately it failed. Sure, you need to incorporate the drivers into your sound server. There is not much magic involved - just link the files as well as your main.c file together and link it with the ddekit, dde_linux26, and dde_linux26_sound libraries. Kind regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIhKLgP5ijxgQLUNkRAr6zAKCRuTS7iYDCfN/jnTVz/bKZsMe4kgCfbqSB W9SYbAmrJ1NZdbldJkeJ/As= =EjGa -----END PGP SIGNATURE-----

1 0

DDE library
by Saya Sheng (盛淑蕙) 09 Jul '08

09 Jul '08

Hi,all Recently, i wrote a simple sound server that only contains DDE initialization routines and tried to compile it with DDE libraries. After checking the Makefile in dde/linux26/lib/src, I guess i need the library 'libdde_linux26_sound.a' to link with, but it seems that i need to write the source code 'sound.c' to map linux functions to DDEKit. How can i implement this? any suggestion or hint? Thank you in advance Saya

2 1

Re: about Conventional Memory Region
by Zhang Yinfei 08 Jul '08

08 Jul '08

Hi Adam, Thanks for the reply. But I cannot find any symbol called find_kip in the fiasco source code. For bootstrap, do you mean those source files in kernel/fiasco/src/boot/ia32/ ？I just want to know where is the source code which start the KIP from scratch . Thanks. Best Regards, Zhang Yinfei On 7/7/08, l4-hackers-request(a)os.inf.tu-dresden.de < l4-hackers-request(a)os.inf.tu-dresden.de> wrote: > > > Date: Sun, 6 Jul 2008 23:51:46 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: about Conventional Memory Region > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20080706215146.GJ7899(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Sun Jul 06, 2008 at 21:49:03 +0800, Zhang Yinfei wrote: > > As in *Mem_region Kip::last_free() const*, the function try to find the > > highest *Conventional* memory region's physical address. (I guess it gets > > physical memory bottom in the first time?). However in *void > > Kip_init::init(),* I only see one Conventional memory region which stores > > virtual address. Where does last_free() get the physical address?? > > > > And in bootstrap, I see it manipulate KIP. I thought at that time, KIP is > > not initialize, because bootstrap runs before Fiasco Startup, where > > Kip_init::init() is called. > > The KIP data structure is indeed in the kernel binary but it is filled > with memory descriptors by bootstrap. I.e. look for find_kip in > bootstrap which looks for the KIP in the kernel. Kip_init::init() does > setup a few things in the KIP but it does not start from scratch with > the memory descriptors. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 63, Issue 5 > ***************************************** >

2 1

about Conventional Memory Region
by Zhang Yinfei 06 Jul '08

06 Jul '08

Hi all, I've got a question about Fiasco source. As in *Mem_region Kip::last_free() const*, the function try to find the highest *Conventional* memory region's physical address. (I guess it gets physical memory bottom in the first time?). However in *void Kip_init::init(),* I only see one Conventional memory region which stores virtual address. Where does last_free() get the physical address?? And in bootstrap, I see it manipulate KIP. I thought at that time, KIP is not initialize, because bootstrap runs before Fiasco Startup, where Kip_init::init() is called. Thanks & Best Regards, Zhang Yinfei

2 1

multi-core support for fiasco? v.s. multi-processor?
by Zhang Yinfei 04 Jul '08

04 Jul '08

Hi all, I've listened to a lecture by Prof. Hermann Haertig about L4 in my university and I'm quite interested in doing some research on L4/Fiasco. I've reviewed some source code of Fiasco recently and one thing I can think of is to add multi-core support for L4/Fiasco. In my investigation, there are some people wrote papers about adding multi-processor (SMP) support for L4 but no one is talking about multi-core support. Is there a big difference between these two in the aspect of fiasco kernel? I'd be very appreciated if you guys can give me some opinions on this. Thanks. Thanks & Best Regards, Zhang Yinfei

3 2

Problem with compiling Fiasco L4 on Suse
by Stefan Kögel 01 Jul '08

01 Jul '08

>>> Can you build with "make V=1" and show the output where the error >>> happens including 20 or more lines above the error? Maybe I can see >>> something there. >>> >>> >>> >>> Adam >> make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib' >> Making all in debug >> make[6]: Entering directory >> `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib/debug' >> /bin/bash ../../libtool --tag=CXX --mode=link g++ -g -O2 -module >> -version-number 0:3:0 -o libdice-debug.la -rpath /home/drops/lib/dice >> init.lo BETrace.lo L4BETrace.lo L4V4BETrace.lo >> g++ -shared -nostdlib >> /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o >> /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o .libs/init.o >> .libs/BETrace.o .libs/L4BETrace.o .libs/L4V4BETrace.o >> -L/usr/lib/gcc/i486-linux-gnu/4.2.3 >> -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib -L/lib/../lib >> -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../.. -lstdc++ >> -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o >> /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o -Wl,-soname >> -Wl,libdice-debug.so.0 -o .libs/libdice-debug.so.0.3.0 >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o: No such >> file or directory >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o: No such file or >> directory >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o: No such file or directory >> g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o: No such >> file or directory >> make[6]: *** [libdice-debug.la] Fehler 1 > > Please delete /home/stefan/Desktop/Fiasco/svn/tudos/dice and check it > out again from svn. That should fix it. > > > > Adam Thank you so much! Worked perfectly. Kind Regards, Stefan

1 0

Problem with compiling Fiasco L4 on Suse
by Stefan Kögel 01 Jul '08

01 Jul '08

> Can you build with "make V=1" and show the output where the error > happens including 20 or more lines above the error? Maybe I can see > something there. > > > > Adam make V=1 PWD=/home/stefan/Desktop/Fiasco/svn/tudos/l4 make -C /home/stefan/Desktop/Fiasco/svn/tudos/l4 O=/home/stefan/Desktop/Fiasco/my-l4-build make[1]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/l4' if [ -r ../dice/Makefile.drops ]; then \ PWD=/home/stefan/Desktop/Fiasco/svn/tudos/l4/../dice make -C ../dice -f Makefile.drops; \ fi make[2]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make all -f GNUmakefile make[3]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make all-recursive make[4]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' Making all in libltdl make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' make all-am make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' make[6]: Für das Ziel »all-am« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/libltdl' Making all in src make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' Making all in be make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' Making all in l4 make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' Making all in v2 make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' Making all in ia32 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/ia32' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/ia32' Making all in amd64 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/amd64' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2/amd64' make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' make[9]: Für das Ziel »all-am« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v2' Making all in v4 make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' Making all in ia32 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4/ia32' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4/ia32' make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' make[9]: Für das Ziel »all-am« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/v4' Making all in fiasco make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' Making all in amd64 make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco/amd64' make[9]: Für das Ziel »all« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco/amd64' make[9]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' make[9]: Für das Ziel »all-am« ist nichts zu tun. make[9]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4/fiasco' make[8]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' make[8]: Für das Ziel »all-am« ist nichts zu tun. make[8]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/l4' Making all in sock make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/sock' make[7]: Für das Ziel »all« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be/sock' make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' make[7]: Für das Ziel »all-am« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/be' Making all in fe make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/fe' make[6]: Für das Ziel »all« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/fe' Making all in parser make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' Making all in idl make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/idl' make[7]: Für das Ziel »all« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/idl' Making all in c-c++ make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/c-c++' make[7]: Für das Ziel »all« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser/c-c++' make[7]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' make[7]: Für das Ziel »all-am« ist nichts zu tun. make[7]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src/parser' make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' if [ -d .svn ]; then \ ver=`svnversion -nc . | /bin/sed -e 's/^[^:]*://;s/[A-Za-z]//'`; \ echo "#define SVNVERSION \"svn r$ver\"" > svnversion.h.new; \ elif [ -s SNAPSHOT ]; then \ ver=`/bin/sed -e '/^Revision: */!d;s///;q' SNAPSHOT`; \ echo "#define SVNVERSION \"svn r$ver\"" > svnversion.h.new; \ else \ touch svnversion.h.new; \ fi if [ -e svnversion.h ]; then \ if [ 0 = `diff svnversion.h svnversion.h.new | wc -l` ]; then \ rm svnversion.h.new; \ else \ mv svnversion.h.new svnversion.h; \ fi; \ else \ mv svnversion.h.new svnversion.h; \ fi make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/src' Making all in include make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' Making all in dice make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include/dice' make[6]: Für das Ziel »all« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include/dice' make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' make[6]: Für das Ziel »all-am« ist nichts zu tun. make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/include' Making all in lib make[5]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib' Making all in debug make[6]: Entering directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib/debug' /bin/bash ../../libtool --tag=CXX --mode=link g++ -g -O2 -module -version-number 0:3:0 -o libdice-debug.la -rpath /home/drops/lib/dice init.lo BETrace.lo L4BETrace.lo L4V4BETrace.lo g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o .libs/init.o .libs/BETrace.o .libs/L4BETrace.o .libs/L4V4BETrace.o -L/usr/lib/gcc/i486-linux-gnu/4.2.3 -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/i486-linux-gnu/4.2.3/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o -Wl,-soname -Wl,libdice-debug.so.0 -o .libs/libdice-debug.so.0.3.0 g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crti.o: No such file or directory g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtbeginS.o: No such file or directory g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/crtendS.o: No such file or directory g++: /usr/lib/gcc/i486-linux-gnu/4.2.3/../../../../lib/crtn.o: No such file or directory make[6]: *** [libdice-debug.la] Fehler 1 make[6]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib/debug' make[5]: *** [all-recursive] Fehler 1 make[5]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice/lib' make[4]: *** [all-recursive] Fehler 1 make[4]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make[3]: *** [all] Fehler 2 make[3]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make[2]: *** [all] Fehler 2 make[2]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/dice' make[1]: *** [../dice] Fehler 2 make[1]: Leaving directory `/home/stefan/Desktop/Fiasco/svn/tudos/l4' make: *** [x] Fehler 2 I appreciate your help. Kind Regards, Stefan

2 1

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 July 2008