- l4-hackers - example.com Site

Re: 16-bit code and L4
by Valery V. Sedletski 20 Jun '07

20 Jun '07

>>> 2) Must all the segment registers be CS == DS == ES == FS == GS == SS == FLAT in L4 usermode >programs (in Intel >>> architecture implementation)? Or, there exist a possibility to use segments other than FLAT? >>> >>Fiasco preserves some of these segments (e.g., GS to support thread >>local storage). However, unless OS/2 makes use of these segments in >>32-bit mode there is no need to change these from a flat setting. > >It seems, that OS/2 does not use GS (GS seems to be always == 0), at least, in application programs. > But also FS is used to address a structure named Thread Info Block (TIB), it is also not flat (it has a limit=0x30) So, FS is used by OS/2 and programs depend on it. GS seems to be not used, and ES and DS are generally flat.

2 1

16-bit code and L4
by Valery V. Sedletski 20 Jun '07

20 Jun '07

Would be someone so kind to answer some questions? These questions are about 16-bit instructions execution on intel processors in L4 usermode programs. First, excuse me for my bad English (it is not native for me). And first I'll try to explain the motivation. -- I am now trying to contribute to the project aiming to create an Opensource OS/2 clone. (osFree aka OS/3 project, http://www.osfree.org/) The goal now is to create OS/2 API implementation with binary compatibility with existing OS/2 (intel) applications. Also, it would be desirable to reuse existing OS/2 device driver base (if it is possible). We are planning to use L4 as a base for API implementation. The problem with existing OS/2 applications is that they are not pure 32-bit; there are many common 16-bit API's now (they are to be replaced with 32-bit analogues in new implementation); almost each LX format executable contains 16-bit fragments (thunks for calling 16-bit API's), though the most of each executable is 32-bit and uses 32-bit flat memory model. Also, most old OS/2 device drivers are 16-bit, they are still very common now (but newer drivers are 32-bit). Another problem is that many drivers and applications are available in binary-only form (so, they cannot be recompiled, as with Linux) 32-bit applications and drivers support can be made, for example, by implementing a converter of LX-executables to pure 32-bits. Also, 16-bit fragments can be executed in a virtual machine. Or, as another variant, it may be possible to execute these 16-bit parts on a real processor. The problem is only how to maintain correct segment registers values and how to add a 16-bit segment descriptor to GDT or LDT. The problem with L4 is that it doesn't expose segmentation to outside the kernel, it abstracts segmentation from usermode programs and only allows to use paging, but not segmentation. The reason is known: segmentation is not portable, it has no analogues on other architectures than intel one. So, the questions are: 1) There is L4Linux. It is mostly 32-bit. But as I know, the Linux kernel also contains some 16-bit parts, such as setup code (it works with BIOS routines and probes hardware), and also (as I heard) acpi suspend/wakeup code. So, it contains 16-bit segments. But doesn't it interfere with L4? How did the people porting Linux to the L4 microkernel solve the problem of 16-bit code? And doesn't it interfere with ELF format capabilities (it is pure 32/64-bit, as I understand)? 2) Must all the segment registers be CS == DS == ES == FS == GS == SS == FLAT in L4 usermode programs (in Intel architecture implementation)? Or, there exist a possibility to use segments other than FLAT? 3) Is it possible to cause the L4 kernel to create 16-bit segment descriptor on Intel architecture?

2 2

Re: Fiasco@ARM - supported hardware
by Daniel Vandersee 19 Jun '07

19 Jun '07

Hi Jorge, I just tried it and it doesn't work for me, too. If I break the program execution after a while it always stops at uart_write+72: > 0xb0002e30 <uart_write+64>: ldr r3, [r2, #32] > 0xb0002e34 <uart_write+68>: tst r3, #4 ; 0x4 > 0xb0002e38 <uart_write+72>: beq 0xb0002e30 <uart_write+64> > 0xb0002e3c <uart_write+76>: ldrb r3, [r0, r12] Did you got it running with skyeye? Attached you will find my skyeye configuration. Maybe you have an idea what goes wrong here? Thanks! Cheers, Daniel Jorge Torres schrieb: > Hi Daniel, > > Have you tried PXA borad with skyeye? > > Thanks, > > JOrge > > On 6/18/07, *Daniel Vandersee* < dvandersee(a)escrypt.com > <mailto:dvandersee@escrypt.com>> wrote: > > Hello, > > how do you test L4 on an ARM platform? Do you have specific hardware > for > that purpose? You mentioned that you use ARM Integrator boards. As there > are several integrator boards available: which one exactly do you use? > Do you use other boards as well? I'm asking because I plan to buy an > ARM > board which is supported out of the box without the need to modify > drivers. > > Do you additionally use software simulators to test L4? If so, which one > do you use? I tried Skyeye to simulate an ARM integrator board as well > as a SA1100-board but didn't get any output over the serial line. Qemu > doesn't work either and terminates with the following error: "qemu: > uncaught target signal 11 (Segmentation fault) - exiting". > > Kind regards, > Daniel > > > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de <mailto:l4-hackers@os.inf.tu-dresden.de> > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > cpu: xscale #cpu: pxa25x mach: pxa_lubbock #cpu: pxa27x #mach: pxa_mainstone mem_bank: map=I, type=RW, addr=0x40000000, size=0x0c000000 mem_bank: map=M, type=RW, addr=0xb0000000, size=0x10000000 #mem_bank: map=M, type=RW, addr=0xd0000000, size=0x00100000 #log: logon=1, logfile=/tmp/sk2.log, start=500000, end=1500000 #lcd:state=on,type=pxa,mod=gtk uart: mod=stdio

1 0

Re: L4Env Building Problem!
by Bjoern Doebel 14 Jun '07

14 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marius.bao wrote: >> Please enter l4/pkg/bootstrap/server/src, run "make V=1" and post the >> complete output here. >> > When I run "make V=1", the make process stops. The output is as follows: > ../../../../mk/Makeconf:120: *** need to give builddir with > O=.../builddir. Stop. Sure, then please run make V=1 O=<path_to_your_builddir> and post the complete output here. > Ps:The ../../../../ directory is l4. > I couldn't compile a package separately. When I want to compile a > single package, I have to enter the build directory to run "make", and > compile all the packages. I suffered a lot as the compile process > takes a long time. You can build (parts of) a single package in at least 2 ways: 1. use the O=<builddir> option when running make just as the error message above tells you. 2. Go to the builddir. There will be a subdirectory pkg with build dirs for all the packages. You can enter these and only build a single one. Regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGcOTNP5ijxgQLUNkRAvWjAJ9ipIMpC2VA1et+nzf2JtJeqaWhLgCfRnb2 E0j6eVEgzO+AZVvOKDrSHL0= =c4iI -----END PGP SIGNATURE-----

1 0

Re: L4Env Building Problem!
by Marius.bao 13 Jun '07

13 Jun '07

Hi, >Could you find out which dice binary is used (run "make V=1" in one of >the idl directories, for instance tudos/l4/pkg/names/idl)? And then run >that binary with the --version option and post the output here? It turned out that i used an old version of DICE, I update to the latest version, and it works correctly. Thanks a lot :) when I compiled the bootstrap package, another problem occured: l4/pkg/bootstrap/server/src/startup.cc:215: undefined reference to `__cxa_guard_release' maybe my gcc is too old. my gcc version is gcc-3.4.2.6-fc3

2 1

L4Env Building Problem!
by Marius.bao 11 Jun '07

11 Jun '07

Hi, Thanks for previous information. I've checkouted l4env using: svn checkout -N http://svn.tudos.org/repos/tudos/trunk tudos cd l4 ./repomgr co l4env When I tried to compile l4env, errors occured in some idl file. eg: names.idl in names package import <l4/sys/types.h> import <l4/names/libnames.h> /** IDL interface of the name server. */ interface names { long register([in, string] char *name); long register_thread([in, string] char *name, [in] l4_threadid_t id); long unregister_thread([in, string] char *name, [in] l4_threadid_t id); long unregister_task([in] l4_threadid_t id); long query_name([in, string] char *name, [out] l4_threadid_t *id); long query_id([in] l4_threadid_t id, [out, string, prealloc_client, max_is(NAMES_MAX_NAME_LEN)] (*) char **name);modified ...... }; errors occured in the last function at the (*) line, the error information is as follows: unknown attribute dice: 1 Error(s) and 0 Warning(s) occured. when I modified the function into long query_id([in] l4_threadid_t id, [out, string] char **name); It compiles OK. I don't know what's the problem as I know little about the corba idl.

2 1

Re: l4-hackers Digest, Vol 50, Issue 7
by Erik Schierboom 09 Jun '07

09 Jun '07

> Message: 4 > Date: Fri, 8 Jun 2007 00:17:26 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: Verify Fiasco assertion using pingpong > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070607221726.GN14071(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Thu Jun 07, 2007 at 13:17:09 +0200, eschierb(a)sci.kun.nl wrote: > >> Quoting Martin Pohlack <mp26(a)os.inf.tu-dresden.de>: >> >> >>> eschierb(a)sci.kun.nl wrote: >>> >>> [...] >>> >>> >>>> "/bin/bash: did_not_find_dice___please_install_dice: command not found" >>>> >>> Did you build Dice? It got moved recently in the SVN from l4/tools/dice >>> to tools/dice. I think you have to build it manually. >>> >>> Cheers, >>> Martin >>> >>> >> I believe I did, by invoking the following commands: >> >> " >> cd dice >> ./bootstrap >> ./configure >> ./make >> " >> > > When being in the l4 directory, does calling > ../dice/src/dice > work or not? I.e. is there a dice binary? > > > > Adam > Calling ../dice/src/dice does work so there is a DICE binary, but when I call "make O=/tmp/build" in the l4 directory I still get the following error: if [ -r ../dice/Makefile.drops ]; then \ make -C ../dice -f Makefile.drops; \ fi make[1]: Entering directory `/tmp/tudos/dice' ../l4/mk/Makeconf:155: Sorry, your object or source path became garbled. ../l4/mk/Makeconf:156: OBJ_BASE: /tmp/build ../l4/mk/Makeconf:157: SRC_BASE_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:158: SRC_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:159: OBJ_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:160: PKGDIR: ../l4/mk/Makeconf:161: L4DIR_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:162: PKGDIR_ABS: ../l4/mk/Makeconf:163: PKGDIR_OBJ: /tmp/tudos/dice ../l4/mk/Makeconf:164: *** Please investigate.. Stop. make[1]: Leaving directory `/tmp/tudos/dice' make: *** [../dice] Error 2

2 1

[Fwd: Re: L4 implementations]
by Sergio Ruocco 08 Jun '07

08 Jun '07

Forwarding my answer below as requested. Sergio -------- Original Message -------- Subject: Re: L4 implementations Date: Fri, 8 Jun 2007 23:15:41 +1200 From: Shams <shams(a)orcon.net.nz> To: <ruocco(a)disco.unimib.it> References: <f3op51$utv$1(a)sea.gmane.org> <4669154F.3020907(a)disco.unimib.it> Hi Sergio Thanks for the info Can you also please post this to the newsgroup so that other newbies can benefit from it too. Thanks Shams ----- Original Message ----- From: "Sergio Ruocco" <ruocco(a)disco.unimib.it> To: "Shams" <shams(a)orcon.net.nz> Sent: Friday, June 08, 2007 8:37 PM Subject: Re: L4 implementations Shams wrote: > Just a few questions which I am having a hard time understanding: For answers to these and other questions, and further information on the L4 microkernel API, its different implementations (Pistachio, Fiasco, OKL4 etc.), and the various OSes running on them (Iguana, DROPS etc.), see also the following web sites: http://en.wikipedia.org/wiki/L4_microkernel_family http://l4hq.org/kernels/ http://l4hq.org/docs/ http://l4hq.org/projects/os/ Pistachio http://l4ka.org/ Fiasco http://os.inf.tu-dresden.de/fiasco/ OKL4 http://www.ok-labs.com/products/ http://portal.ok-labs.com/ and this paper of mine: http://ertos.nicta.com.au/publications/papers/Ruocco_06.abstract.pml http://citeseer.ist.psu.edu/757180.html Best Regards, Sergio -- Sergio Ruocco, PhD Research Fellow sergio.ruocco(a)disco.unimib.it / gmail.com NOMADIS Lab. phone: +39-02-6448-7879 mobile, embedded real-time systems skype: 'sergioruocco' Università degli Studi di Milano-Bicocca, Italy

1 0

L4 implementations
by Shams 08 Jun '07

08 Jun '07

Hi I played with the demo cd and it works great.. Just a few questions which I am having a hard time understanding: 1. L4 is itself a API/ABI reference, right? 2. Are L4.Pistachio and L4.Fiasco are 2 different implementations of L4? 3. Is L4.Pistachio is the current official reference implementation? Do both of them only differ in internal code only? 3. What is the difference between L4.Pistachio and L4.Fiasco? Why are there 2 separate implementations ie. why not just one codebase? Are you able to merge these 2 together or plan to? 4. Is L4.Sec official and already in the process of being implemented? Is L4.Pistachio and L4.Fiasco going to be replaced by L4.Sec? Thanks Shams

6 15

Verify Fiasco assertion using pingpong
by eschierb＠sci.kun.nl 08 Jun '07

08 Jun '07

Hi, I am trying to achieve a very simple thing, which is to test an assertion in the Fiasco ICP path. More specifically, I want to add the following assertion to the sys_ipc() function: " // This assertion is added by us assert(!(state() & Thread_polling)); if (EXPECT_TRUE(have_send_part || have_receive_part)) ret = do_ipc(have_send_part, partner, have_receive_part, sender, t, regs); " As can be seen, I want to assert that the Thread_polling bit is not set before calling do_ipc(). I planned to do this by compiling the modified Fiasco kernel and the pingpong package. If the assertion would not fire after running the pingpong test suite, I would have at least some confidence that the assertion does not hold. I have already done something similar a while ago, but with the newer versions I cannot seem to get it working. The first problem was with the DICE compiler, if I used the latest version of the DICE compiler I got the "collect2: ld returned 1 exit status". I solved this by using the 3.1.1 DICE version. I then used the following commands: " svn co http://svn.tudos.org/repos/tudos/tags/dice/3.1.1 dice ./repomgr co hello cd dice ./bootstrap ./configure ./make cd .. cd l4/pkg svn up pingpong cd .. make O=/tmp/build config make O=/tmp/build " However, this resulted in the following error " if [ -r ../dice/Makefile.drops ]; then \ make -C ../dice -f Makefile.drops; \ fi make[1]: Entering directory `/tmp/tudos/dice' ../l4/mk/Makeconf:155: Sorry, your object or source path became garbled. ../l4/mk/Makeconf:156: OBJ_BASE: /tmp/build ../l4/mk/Makeconf:157: SRC_BASE_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:158: SRC_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:159: OBJ_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:160: PKGDIR: ../l4/mk/Makeconf:161: L4DIR_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:162: PKGDIR_ABS: ../l4/mk/Makeconf:163: PKGDIR_OBJ: /tmp/tudos/dice ../l4/mk/Makeconf:164: *** Please investigate.. Stop. make[1]: Leaving directory `/tmp/tudos/dice' make: *** [../dice] Error 2 " As an alternative to the last three lines, I tried to issue the "make O=/tmp/build" command in the l4/pkg directory. This resulted in the following error: "/bin/bash: did_not_find_dice___please_install_dice: command not found" Any idea how this can be remedied? With regards, Erik Schierboom

3 3

Re: Hiworld Problem
by Bjoern Doebel 06 Jun '07

06 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, >> Did you checkout and build the L4 Environment (as requested in chapter >> 2 of >> the tutorial)? If so, generic_ts should be built and your application >> gets >> linked with it. > I followed http://os.inf.tu-dresden.de/drops/download.html using svn to > check > out the hello module. I think it contains everything necessary. I just > unzipped it and > compiled it. No it doesn't. The hello module includes the minimal stuff necessary to build an L4 application. As stated in the BID tutorial, chapter 1, please checkout the L4Env module and compile it. Thereafter everythin should work fine. Regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGZqeyP5ijxgQLUNkRAjA8AJwIMFk71NoJrdjeGEkyBKmA/gTtkACePNgF lXoytPeJXVrx+EJK6qN/kf4= =pOPl -----END PGP SIGNATURE-----

1 0

Hiworld Problem
by Marius.bao 06 Jun '07

06 Jun '07

Hi all, I followed the tutoral--<<Building Infrastructure for DROPS (BID) Tutorial>>(http://os.inf.tu-dresden.de/l4env/doc/html/bid-tut/node3.html) to wirte my fisrt "hiworld" server. I've used the template, ˜/src/l4/pkg/hiworld> ../../mk/tmpl/inst The "hiworld" source file is as follows: #include <stdio.h> int main(int argc, char** argv){ printf("HiWorld"); return 0; } An error occured when I compiled the server. I think it might be a link error. /usr/bin/ld: cannot find -lgeneric_ts ==> Linking hiworld LD_PRELOAD=/home/hector/Develop/L4-2007/l4/tool/gendep/libgendep.so GENDEP_TARGET=hiworld GENDEP_BINARY=ld gcc -o hiworld /home/hector/Develop/L4-2007/l4/build/lib/x86_586/crt0.o main.o -Ttext=0x01800000 -L/home/hector/Develop/L4-2007/l4/build/lib/x86_586/l4v2 -L/home/drops/lib/x86_586/l4v2 -L/home/hector/Develop/L4-2007/l4/build/lib/x86_586 -L/home/drops/lib/x86_586 -L/home/hector/Develop/L4-2007/l4/build/lib -L/home/drops/lib -T/home/hector/Develop/L4-2007/l4/build/lib/x86_586/main_stat.ld -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i386-redhat-linux/3.4.2/libgcc.a -luc_c -ll4sys -Ttext=0x01800000 -Wl,--warn-common -Wl,-gc-sections /usr/bin/ld: cannot find -lgeneric_ts collect2: ld returned 1 exit status make[6]: *** [hiworld] error 1 make[6]: Leaving directory `/home/hector/Develop/L4-2007/l4/build/pkg/hiworld/server/src/OBJ-x86_586-l4v2' make[5]: *** [/home/hector/Develop/L4-2007/l4/build/pkg/hiworld/server/src/OBJ-x86_586-l4v2] error 2 make[5]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg/hiworld/server/src' make[4]: *** [src] error 2 make[4]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg/hiworld/server' make[3]: *** [server] error 2 make[3]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg/hiworld' make[2]: *** [hiworld.bin] error 2 make[2]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg' make[1]: *** [pkg] error 2 make[1]: Leaving directory `/home/hector/Develop/L4-2007/l4' make: *** [x] error 2 I wonder how to write the makefile myself without using the template. When I compile the "Hiworld" server, what other files(source files,head files) should I need to include.

2 1

PANIC
by Davide Fasoli 01 Jun '07

01 Jun '07

the problem was the vbeset command, i used the --vbemode=0x117 option in the con module and l4 booted correctly, thanks a lot for helping me. ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

1 0

PANIC
by Davide Fasoli 01 Jun '07

01 Jun '07

2 1

double page-fault
by Davide Fasoli 31 May '07

31 May '07

this is my bootloader setup for booting fiasco title Fiasco, Console, Loader, Tiny Shell (run) root (hd0,2) kernel /boot/fiasco_mod/bootstrap -modaddr 0x02000000 module /boot/fiasco_mod/fiasco -nowait -serial_esc -comspeed 115200 -comport 1 module /boot/fiasco_mod/sigma0 module /boot/fiasco_mod/roottask module /boot/fiasco_mod/names --events module /boot/fiasco_mod/log --events module /boot/fiasco_mod/dm_phys --isa=0x00800000 -v --events module /boot/fiasco_mod/con module /boot/fiasco_mod/simple_ts -t 300 --events module /boot/fiasco_mod/tftp #The loader should load and start the minishell module /boot/fiasco_mod/loader module /boot/fiasco_mod/run vbset 0x117 boot it returns me an error of Double Page Fault, how can i fix it? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

region overlap
by Davide Fasoli 30 May '07

30 May '07

Now it starts, but it gives me a "region overlap error", i've tryed searching something about it and i've seen that the modaddr command is not a grub command, how can i make things work in a grub bootloader? i've heard about a single-image mode, how can i make it work? thanks in advance, Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

3 2

Re: perf_p6 error
by Davide Fasoli 30 May '07

30 May '07

Hi, thanks the problem is resolved. Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

1 0

perf_p6 error
by Davide Fasoli 30 May '07

30 May '07

Compiling it gives me that error: make[3]: Entering directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples' test -f perf/broken -o -f perf/obsolete || \ if [ -f perf/Makefile ] ; then PWD=/home/fasoz/soa/tudos/l4/pkg/l4util/examples/perf make -C perf ; fi make[4]: Entering directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples/perf' PWD=/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2 make -C /home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2 -f Makefile make[5]: Entering directory `/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2' ==> Linking perf_p6 LD_PRELOAD=/home/fasoz/soa/tudos/l4/prova/tool/gendep/libgendep.so GENDEP_TARGET=perf_p6 GENDEP_BINARY=ld ld -o perf_p6 /home/fasoz/soa/tudos/l4/prova/lib/x86_586/crt0.o p6.o -Ttext=0xa00000 -L/home/fasoz/soa/tudos/l4/prova/lib/x86_586/l4v2 -L/home/fasoz/soa/tudos/l4/prova/lib/x86_586 -L/home/fasoz/soa/tudos/l4/prova/lib -L/home/drops/lib/x86_586/l4v2 -L/home/drops/lib/x86_586 -L/home/drops/lib -T/home/fasoz/soa/tudos/l4/prova/lib/x86_586/main_stat.ld -static -lmain -ll4util -ll4sys -nostdlib -luc_c -luc_be_minimal_io -luc_be_l4_start_stop -lc_be_sigma0_mem -luc_c -luclibc_support -ll4util -lsigma0 -luc_c /usr/lib/gcc/i486-linux-gnu/4.1.2/libgcc.a -luc_c -ll4sys -Ttext=0xa00000 --warn-common -gc-sections /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(vfprintf.o): In function `vfprintf': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/stdio/_vfprintf.c:1948: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(wcrtomb.o): In function `wcrtomb': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/misc/wchar/wchar.c:365: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(wcsnrtombs.o): In function `wcsnrtombs': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/misc/wchar/wchar.c:917: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(_fpmaxtostr.o): In function `_fpmaxtostr': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/stdio/_fpmaxtostr.c:769: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(_ppfs_parsespec.o): In function `_ppfs_parsespec': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/stdio/_vfprintf.c:1155: undefined reference to `__stack_chk_fail' make[5]: *** [perf_p6] Error 1 make[5]: Leaving directory `/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2' make[4]: *** [/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples/perf' make[3]: *** [perf] Error 2 make[3]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples' make[2]: *** [examples] Error 2 make[2]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg/l4util' make[1]: *** [l4util.bin] Error 2 make[1]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg' make: *** [pkg] Error 2 what about that error? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 2

Re: multiple compilations
by Davide Fasoli 30 May '07

30 May '07

If i compile without "/home/fasoz/soa/tudos/kernel/fiasco/src/boot/ia32/boot.S" gcc -c -MD -MP -MF .boot.S.d.new -o boot.o -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -DASSEMBLER gcc: unrecognized option `-MP' gcc: unrecognized option `-MF' gcc: .boot.S.d.new: linker input file unused since linking not done but, if I use: g++ -c -MD -MP -MF .boot.S.d.new -o boot.o -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -DASSEMBLER /home/fasoz/soa/tudos/kernel/fiasco/src/boot/ia32/boot.S it compiles, where can I modify the makefile??? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

Re: multiple compilations
by Davide Fasoli 28 May '07

28 May '07

----- Messaggio originale ----- Da: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> A: l4-hackers(a)os.inf.tu-dresden.de Inviato: Lunedì 28 maggio 2007, 13:21:55 Oggetto: Re: multiple compilations On Mon May 28, 2007 at 11:04:55 +0000, Davide Fasoli wrote: > On Mon May 28, 2007 at 09:15:43 +0200, Davide Fasoli wrote: > > I've installed fiasco following the step of the howto I've found > > here(http://os.inf.tu-dresden.de/fiasco/use.html) from > > this(http://os.inf.tu-dresden.de/drops/download.html) repository, i've > > tried following the hints you gave me but still no results. > > I'm sure you exactly followed the howto but again, what Linux > distribution are you using? > > Ubuntu 6.10; > > I'd also like to know which version of gcc, > > gcc 2.95.2 > gcc 3.3 > gcc 3.4 > gcc 4.1 > > binutils > > No > > and make > > make 3.81 Ok, thanks. Can please issue 'make -C /home/fasoz/soa/tudos/kernel/fiasco/build V=1' and post the output? The output is this: make: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 make[1]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' Checking compiler config... .Compiler-config is unchanged unchanged. make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all make[1]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' if [ -d /home/fasoz/soa/tudos/kernel/fiasco/src/.svn ]; then \ v=`svnversion -nc /home/fasoz/soa/tudos/kernel/fiasco/src`; v=${v%[A-Z]}; \ echo "#define CODE_VERSION \"r${v#*:}\"" > version.h; \ else \ echo "#define CODE_VERSION \"rUNKNOWN\"" > version.h; \ fi -e ... Making kip.o g++ -c -MD -MP -MF .kip.cc.d.new -o kip.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip.cc -e ... Making kip-ia32.o g++ -c -MD -MP -MF .kip-ia32.cc.d.new -o kip-ia32.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip-ia32.cc -e ... Making kip-debug.o g++ -c -MD -MP -MF .kip-debug.cc.d.new -o kip-debug.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip-debug.cc -e ... Making kip-ia32-debug.o g++ -c -MD -MP -MF .kip-ia32-debug.cc.d.new -o kip-ia32-debug.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip-ia32-debug.cc -e ==> Archiving into libabi.a rm -f libabi.a ar crs libabi.a kip.o kip-ia32.o kip-debug.o kip-ia32-debug.o l4_types.o l4_types-iofp.o l4_types-32bit.o l4_types-debug.o l4_types-caps.o utcb-ia32-ux.o -e ... Making boot.o gcc -c -MD -MP -MF .boot.S.d.new -o boot.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -DASSEMBLER /home/fasoz/soa/tudos/kernel/fiasco/src/boot/ia32/boot.S gcc: cannot specify -o with -c or -S and multiple compilations make[1]: *** [boot.o] Error 1 make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make: *** [all] Error 2 make: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > Thanks. > > > Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> ha scritto: Hi, > > > > On Fri May 25, 2007 at 13:47:33 +0200, Davide Fasoli wrote: > > > when running this command from shell > > > > > > make O=/home/fasoz/soa/tudos/l4/prova > > > > > > where /home/fasoz/soa/tudos/l4/prova is the installation directory of l4, I had the following text as output: > > > > > > ... > > > make -C build > > > make[2]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 > > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > Checking compiler config... unchanged. > > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all > > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > -e ... Making kip.o > > > -e ... Making kip-ia32.o > > > -e ... Making kip-debug.o > > > -e ... Making kip-ia32-debug.o > > > -e ==> Archiving into libabi.a > > > -e ... Ma king boot.o > > > gcc: cannot specify -o with -c or -S and multiple compilations > > > make[3]: *** [boot.o] Error 1 > > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make[2]: *** [all] Error 2 > > > make[2]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make[1]: *** [build] Error 2 > > > make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco' > > > make: *** [../kernel/fiasco] Error 2 > > > > > > I was wondering about what can cause this error, i spent something > > > like 15 days on this without coping on... could you please help me? I > > > need to install l4 for an exam... > > > > Just plain building the kernel with the default setup works just fine > > for me. Which distribution are you using? > > And build with more output with "make V=1". Doing this in the > > kernel/fiasco/build directory is sufficient. 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 thanks ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

Re: multiple compilations
by Davide Fasoli 28 May '07

28 May '07

Hi, ----- Messaggio originale ----- Da: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> A: l4-hackers(a)os.inf.tu-dresden.de Inviato: Lunedì 28 maggio 2007, 11:43:35 Oggetto: Re: multiple compilations Hi, On Mon May 28, 2007 at 09:15:43 +0200, Davide Fasoli wrote: > I've installed fiasco following the step of the howto I've found > here(http://os.inf.tu-dresden.de/fiasco/use.html) from > this(http://os.inf.tu-dresden.de/drops/download.html) repository, i've > tried following the hints you gave me but still no results. I'm sure you exactly followed the howto but again, what Linux distribution are you using? Ubuntu 6.10; I'd also like to know which version of gcc, gcc 2.95.2 gcc 3.3 gcc 3.4 gcc 4.1 binutils No and make make 3.81 are you using, and I'd like to see the build done with V=1. Thanks. > Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> ha scritto: Hi, > > On Fri May 25, 2007 at 13:47:33 +0200, Davide Fasoli wrote: > > when running this command from shell > > > > make O=/home/fasoz/soa/tudos/l4/prova > > > > where /home/fasoz/soa/tudos/l4/prova is the installation directory of l4, I had the following text as output: > > > > ... > > make -C build > > make[2]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > Checking compiler config... unchanged. > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > -e ... Making kip.o > > -e ... Making kip-ia32.o > > -e ... Making kip-debug.o > > -e ... Making kip-ia32-debug.o > > -e ==> Archiving into libabi.a > > -e ... Ma king boot.o > > gcc: cannot specify -o with -c or -S and multiple compilations > > make[3]: *** [boot.o] Error 1 > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make[1]: *** [build] Error 2 > > make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco' > > make: *** [../kernel/fiasco] Error 2 > > > > I was wondering about what can cause this error, i spent something > > like 15 days on this without coping on... could you please help me? I > > need to install l4 for an exam... > > Just plain building the kernel with the default setup works just fine > for me. Which distribution are you using? > And build with more output with "make V=1". Doing this in the > kernel/fiasco/build directory is sufficient. > 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 Thanks. Davide ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

multiple compilations
by Davide Fasoli 28 May '07

28 May '07

I'm writing this mail about some problem i had during the l4 microkernel installation.. when running this command from shell make O=/home/fasoz/soa/tudos/l4/prova where /home/fasoz/soa/tudos/l4/prova is the installation directory of l4, I had the following text as output: ... make -C build make[2]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' Checking compiler config... unchanged. make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' -e ... Making kip.o -e ... Making kip-ia32.o -e ... Making kip-debug.o -e ... Making kip-ia32-debug.o -e ==> Archiving into libabi.a -e ... Ma king boot.o gcc: cannot specify -o with -c or -S and multiple compilations make[3]: *** [boot.o] Error 1 make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make[1]: *** [build] Error 2 make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco' make: *** [../kernel/fiasco] Error 2 I was wondering about what can cause this error, i spent something like 15 days on this without coping on... could you please help me? I need to install l4 for an exam... thanks in advance Davide Fasoli --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

2 4

Can we install L4 on a "bare machine"?
by Marius.bao 26 May '07

26 May '07

Hi everybody, I have installed L4 under Linux successfully. Now I wonder can we install L4 on a "bare machine"--a computer which haven't installed any OS at all. If we can, then how to install it. If not, what extra job should I do to make it possible. As I'm thinking of that L4 is just a microkernel, it hasn't got a filesystem, if we want to install it on a "bare machine", how shall we manage the files.

2 1

Re: The boot error of L4Linux
by chenggh 24 May '07

24 May '07

On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > Hi: > > > When I boot the L4Linux there are some errors. In this mail there are > > > 2 attachments of linux26.cfg, grub configuration and boot log. Please > > > help me to check the boot log. > > > > The new boot log is as following: > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > 0x000 > > l4lx : 04000) > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > You probably need 'allow_vga' in your l4linux loader configuration file. The error is same when I add the "allow_vga" in linux26.cfg like this: modpath "(hd0,1)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M root=/dev/hda2" all_sects_writable allow_vga The boot log is : names | Starting threaistening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:17:44:03 DMphys | DMphys memory ap: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPhys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x000x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Wed Ma l4lx : y 23 16:40:01 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b7480 [429kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread wiection: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for mai memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x0E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thanks. cheng

1 0

Re: The boot error of L4Linux
by Christian Helmuth 24 May '07

24 May '07

Hi, On Thu, May 24, 2007 at 03:24:07PM +0000, chenggh wrote: > The error is same when I add the "allow_vga" in linux26.cfg like this: Any news since you followed Adam's suggestion (use one line per option)? If you were successful, the readers of this ML would benefit from your experiences. Cheers -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0