- l4-hackers - example.com Site

Adapting L4 to automake
by Juho Östman 08 Jun '00

08 Jun '00

I think it would be useful to adapt L4 building system to GNU automake and autoconf as I have written earlier. I have now done preliminary modification to the source tree and I'd like to know how should I continue. I already have a source tree which builds the Fiasco kernel, rmgr, sigma0 and hello server using automake generated Makefiles. There is also a lot of need of finishing up. For example it doesn't create distribution packages completely using 'make dist'. The source tree package was so large that I didn't want to post it to this mailing list but I could send it anyone who is willing to look at it.

2 1

build problems
by Edmund GRIMLEY EVANS 23 May '00

23 May '00

I've just spent some time trying to build Fiasco from the CVS source. (1) It would be nice if the build instructions and FAQ could be put with the source in CVS for the benefit of people who have to dial up. (2) The build instructions don't tell you to build oskit10 first. (3) I found I needed gcc-2.7.2.3 to build oskit10, and I had to make the following changes to make it compile: - remove HAVE_CODE16 from oskit/config.h - remove have_code16 from Makeconf - remove in2000 from oskit/dev/linux_scsi.h Which assember are other people using to build this? I'm using: GNU assembler version 2.9.5 (i386-linux) using BFD version 2.9.5.0.37 (4) I used egcs-1.1.1 to build l4, and had a series of makefile problems which might be very easy for someone else to fix. A complete log of the errors I got and how I worked around them is given below. (5) The build instructions then tell you to cd to kernel/fiasco/src and make again, but this was already done by make in l4/. (I'll tell you about my run-time problems when I try it ...) Edmund make[4]: *** No rule to make target `../../../../include/l4/log/l4log.h', needed by `.p6.c.d'. Stop. make[4]: Leaving directory `/home/ege/aferoj/l4-cvs/l4/pkg/l4util/examples/perf' $ mkdir include/l4/log ; cp -i pkg/log/include/l4/log/l4log.h include/l4/log ld -N -Ttext 0x430000 -o perf_p6 p6.o crt0.o -L../../../../lib -L../../../../../oskit/lib -L/home/drops/lib -llog -ll4util -lpci -lmc -lnames -loskit_support -lkern -lmc -lrmgr -llmm ld: cannot find -llog make[4]: *** [perf_p6] Error 1 make[4]: Leaving directory `/home/ege/aferoj/l4-cvs/l4/pkg/l4util/examples/perf' $ ( cd lib ; ln -s ../pkg/log/lib/src/liblogserver.a ../pkg/log/lib/src/liblog.a .) ld -N -Ttext 0x430000 -o perf_p6 p6.o crt0.o -L../../../../lib -L../../../../../oskit/lib -L/home/drops/lib -llog -ll4util -lpci -lmc -lnames -loskit_support -lkern -lmc -lrmgr -llmm ld: cannot find -lpci make[4]: *** [perf_p6] Error 1 make[4]: Leaving directory `/home/ege/aferoj/l4-cvs/l4/pkg/l4util/examples/perf' $ touch pkg/l4util/examples/perf/perf_p6 # It finishes building now, but we don't have perf_p6, so: $ rm pkg/l4util/examples/perf/perf_p6 ld -N -Ttext 0x430000 -o perf_p6 p6.o crt0.o -L../../../../lib -L../../../../../oskit/lib -L/home/drops/lib -llog -ll4util -lpci -lmc -lnames -loskit_support -lkern -lmc -lrmgr -llmm ld: cannot find -lpci make[4]: *** [perf_p6] Error 1 make[4]: Leaving directory `/home/ege/aferoj/l4-cvs/l4/pkg/l4util/examples/perf' # cd to that directory and do the link without -lpci # now everything is built, I think

2 2

building linux22
by Edmund GRIMLEY EVANS 22 May '00

22 May '00

And could someone please tell me what symbolic links I should create to build linux22? I assume that's what missing after I did cvs update -d. In particular, what should linux22/include/asm point at, and where should linux22/include/asm-l4/param.h find <asm/l4arch/param.h>? Edmund

2 1

Re: l4/log/l4log.h
by Michael Hohmuth 20 May '00

20 May '00

Juho Östman <jostman(a)myrealbox.com> writes: > It seems that the file 'l4log.h' is missing in the CVS distribution. > Where is it found? I have added the "log" package to the CVS distribution. (We recently introduced a dependency on the "log" package in the code we distribute; I think there even are some cross dependencies between packages... the easy fix for now just seems to be distributing the "log" package as well. :-) Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

l4/log/l4log.h
by Juho Östman 15 May '00

15 May '00

It seems that the file 'l4log.h' is missing in the CVS distribution. Where is it found?

1 0

Re: Plaese .. Could you help me ?
by Michael Hohmuth 14 Apr '00

14 Apr '00

Ricky, Jean just went into his well-deserved weekend, but he told me to tell you that he has tried your boot disk, and has been able to reproduce your problem. He got it to run by replacing your Fiasco binary with a newer version of Fiasco. So you are probably using an outdated version of the kernel. You should download a newer version from our remote-CVS server (see <URL:http://os.inf.tu-dresden.de/drops/download.html for instructions). Michael Jean Wolter <jean.wolter(a)inf.tu-dresden.de> writes: > "Ricky(Soohyung) Lee" <onlyjazz(a)cselab.snu.ac.kr> writes: > > > But, I have another problem. > > When I boot from the grub floppy disk with glinux.gz on it, > > after the message that is saying the first task is created, > > the kernel fall into the endless loop with printing out " root: rcvd > > b9002, 4bc10c, src :5.3 ". > > Would it be possible to gzip the boot disk and send it to us? Then we > could try to boot it and see, what fails. > > I´m not quite sure that I understand the scenario good enough to come > up with an explanation and a fix. Somehow the service thread (5.3) > touches a page in the adapter area (a0000-100000) and doesn´t get or > doesn´t have a mapping for it. > > Jean -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Re: Plaese .. Could you help me ?
by Jean Wolter 14 Apr '00

14 Apr '00

"Ricky(Soohyung) Lee" <onlyjazz(a)cselab.snu.ac.kr> writes: > But, I have another problem. > When I boot from the grub floppy disk with glinux.gz on it, > after the message that is saying the first task is created, > the kernel fall into the endless loop with printing out " root: rcvd > b9002, 4bc10c, src :5.3 ". Would it be possible to gzip the boot disk and send it to us? Then we could try to boot it and see, what fails. I´m not quite sure that I understand the scenario good enough to come up with an explanation and a fix. Somehow the service thread (5.3) touches a page in the adapter area (a0000-100000) and doesn´t get or doesn´t have a mapping for it. Jean -- I get up each morning, gather my wits. Pick up the paper, read the obits. if I'm not there I know I'm not dead. So I eat a good breakfast and go back to bed. Peete Seeger

1 0

Plaese .. Could you help me ?
by Ricky(Soohyung) Lee 14 Apr '00

14 Apr '00

Hi, everyone ! First of all, let me introduce myself . My name is Ricky Lee . I'm in the course of master's degree at Seoul National University in Korea. Thesedays I'm reading L4-related papers. And, I'm trying to make experience on L4Linux on Fiasco. But, It is not so easy for me. Today, I finally succeeded in building linux22. I really appreciate Michael Hohmuth' advices. But, I have another problem. When I boot from the grub floppy disk with glinux.gz on it, after the message that is saying the first task is created, the kernel fall into the endless loop with printing out " root: rcvd b9002, 4bc10c, src :5.3 ". I guess that it is printed out from root_pager() in l4_paper.c Can you tell me what's wrong ? And, then, what should I do? I really need to solve this problem. So, I really need your help. Please, Help me .. Thanks for your kindness . Thanks . P.S. I compiled Fiasco and Linux22 server on the Redhat package 5.2. Its kernel version is 2.0.36. Any software requirement that is mentioned in the L4linux homepage was met, I think . Can there be the reason of problem with the linux environment in which I compiled those sources ? Can anyone tell me the kernel version and H/W spec. on which you've built the L4Linux22 Server ? It'll be very helpful to me if you tell me them .. Please !!! Thank you very much !! - Ricky Lee -

1 0

IPC & invalid Thread-ID
by Christian Stueble 03 Mar '00

03 Mar '00

-----BEGIN PGP SIGNED MESSAGE----- Hello, what happens if IPC uses an invalid thread-id? Is the message although forwarded to the subsystem's chief? Ciao, Chris -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble(a)ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: J7gRC3CpAZgh3vXKJpAlEFSfZz45w/ET iQCVAwUBOL5y5fyJjJy/cQT1AQFaywQAhBB4KcN8eHZXMrAPgrvJyQhbEMoRYc6j Wmpt5tBK3Tu1DmcNtTqlcGChzFIDrUiE6+Iw8eN74Bx2Dn+Cn+ohcUmSeaxEjkNl 2F8rTA/13dm/4wojmRz87uAvHWuFx+PycsXm7P3BRRqb+9aC+O1ftau6bNSqsmXC 8A/QvdUxDQg= =PFys -----END PGP SIGNATURE-----

2 3

autoconf
by Juho Östman 28 Feb '00

28 Feb '00

What do you think about adapting L4 (and Fiasco) to use autoconf? The most important immediate benefits are the possibility of using a separate build directory and configuration options. And it would be more compatible with GNU build mechanisms. If you think that is a good idea I could be voluntary to make necessary changes.

1 0