make
' on your system, substitute its name in the
examples below.
python
.
To run Fiasco, you need:
The steps nessecary to build a Fiasco kernel are as follows:
Get Fiasco and needed modules from our read-only SVN.
How to get all the needed modules from our SVN is described on the Get DROPS page.
a) Checkout the hello module to get everything (Recommended):
The hello module contains more than what is actually needed, so don't be scared!
b) If you're only interested in Fiasco itself (i.e. compile without Roottask, Sigma0, etc.), the following suffices:
Don't call make
in the l4/tool/preprocess
directory, it won't work because of the missing l4 checkout and it's NOT
necessary to build Fiasco!
make -C l4 O=/my-user-build-dir oldconfig
Most likely you do not need to change anything, so
oldconfig
is ok. If you want to change something you
may also take the config
target.
/my-user-build-dir
is any directory you like. That's the location
where any generated file will be put in.
a) Compilation when you've checked out the whole L4 tree:
cd l4
make O=/my-user-build-dir
This will build all packages that you have checked out and that
are necessary to run Fiasco with some programs.
b) When building Fiasco only:
Nothing needs to be done here, proceed with the next point.
Compile Fiasco.
First, create a build directory using:
cd kernel/fiasco
make BUILDDIR=/my-kernel-build-dir
The path given to make BUILDDIR=
can either be absolute or
relative to kernel/fiasco
.
Now change to your build directory to configure the kernel.
cd /my-kernel-build-dir
make menuconfig
With make menuconfig
the kernel configurator will be
started. You can now configure your kernel.
Use the 'h' key to get help, use the arrow
keys to navigate through the menus and space to switch the options, use
'x' to save and exit.
At this stage, your kernel should be properly configured, so you
can proceed to building it:
make
This should create a binary named `main
' and
symbolic link fiasco
pointing to main
.
An even faster way to build a preconfigured fiasco kernel is to go
to kernel/fiasco
and call make fiasco
:
cd kernel/fiasco
make fiasco
This will build a fiasco kernel with the ia32-short template in the
kernel/fiasco/build
directory.
Note:
If you're looking for Fiasco-UX (the Fiasco port to Linux User space),
you probably want to take a look at its own page.
<builddir>/bin/$(ARCH)/bootstrap
.$(ARCH)
is something like x86_586
and
$(L4API)
is something like l4v2
.
/my-kernel-build-dir/fiasco
.
<builddir>/bin/$(ARCH)/$(L4API)/sigma0
.
Roottask also has been built in step 2 in the previous section. The
Roottask binary can be found at
<builddir>/bin/$(ARCH)/$(L4API)/roottask
.
<builddir>/bin/$(ARCH)/$(L4API)/hello
.The L4Linux server is another very popular Fiasco application program.
For the examples below, I'll assume you use the courtesy GRUB boot floppy we provide (see the download page for details).
menu.lst
file looks as follows:
title hello world
kernel (fd0)/bootstrap
modaddr 0x02000000
module (fd0)/fiasco -nokdb
module (fd0)/sigma0
module (fd0)/roottask
module (fd0)/hello
When booted, you should see the hello word server repeatedly printing its thread id.
Some notes:
-nokdb
" option for Fiasco
(see step 3 in the previous section), Fiasco would enter a
kernel breakpoint at startup and try to connect to a remote GDB
connected via a serial line (COM1).
fiasco/src/.gdbinit
to
match your host's serial port, remove the "-nowait
" boot
option from your GRUB config file, reboot Fiasco, and start your GDB
(or your favorite GDB-based debugger) when the "KDB: init" message
appears. You can then set breakpoints, continue the execution, and
even interrupt Fiasco by typing Control-C in the debugger.
Another way to debug Fiasco is using Fiasco's built-in low-level
debugger. This debugger has its own manual, which you can find on the
documentation page.
Developing for Fiasco
To develop applications for Fiasco, you can use the L4 development
environment, including some libraries in l4/lib
. The
most important library is Libl4sys which provides C bindings for L4
system calls.
For more information, please visit the L4/x86 Developer's Resources page, and have a look at the Libl4sys manual pages.
If you are developing for L4, we also suggest that you subscribe to the L4-Hackers mailing list.
Reporting a bug in Fiasco
To report a bug in the Fiasco µ-kernel, please use
the l4-hackers mailing list.
This document
If you have corrections or additions to this document, please send them to
its current maintainer Adam.
Thanks.