l4-hackers November 2010

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

12 participants
20 discussions

Building L4linux
by Maxime Lastera 07 Nov '10

07 Nov '10

Hi, I have built succefully L4linux. I have used the snapshot version. So now I want to run it, but I don't have tftboot directory in l4linux tree. I can't follow the example because I don't have many modules like names l4io a vmlinuz file is in l4linux tree. what are the steps to boot on L4linux from harddrive ? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

3 3

l4linux on arm11mpcore (build error)
by Rahul Ramasubramanian 07 Nov '10

07 Nov '10

Hi I am trying to build l4linux for arm. I have already built and tested l4re and the fiasco kernel (generated a simple image using the hello.lua script) After pulling the l4linux sources from svn , i used the following steps (as described in the wiki) 1> l4linux-2.6$ make O=/tmp/buildpath L4ARCH=arm CROSS_COMPILE=arm-linux- arm_defconfig 2>l4linux-2.6$ make O=/tmp/buildpath L4ARCH=arm CROSS_COMPILE=arm-linux- menuconfig In menuconfig , i gave the correct path for l4 build dirctory ( in my case it is /home/syslab1/l4fiasco/src/l4/build). This is the directory which hosuses the images folder etc after the l4re and the simple hello image was built. I also selected the arm architecture 3>l4linux-2.6$ make O=/tmp/buildpath L4ARCH=arm CROSS_COMPILE=arm-linux- I get the following error when i run the last command syslab1@syslab1-desktop:~/l4fiasco/l4linux$ make O=/tmp/l4linuxbuild/ L4ARCH=arm CROSS_COMPILE=arm-linux- L4 source directory: /home/syslab1/l4fiasco/src/l4 PWD=/home/syslab1/l4fiasco/src/l4 make -C /home/syslab1/l4fiasco/src/l4 -f /home/syslab1/l4fiasco/l4linux/arch/l4/Makefile.l4conf O=/home/syslab1/l4fiasco/src/l4/build L4X_LOOP_CHECK=1 OUTPUT=/tmp/l4linuxbuild/Makeconf.l4conf GEN /tmp/l4linuxbuild/Makeconf.l4conf GEN /tmp/l4linuxbuild/Makefile scripts/kconfig/conf -s arch/l4/Kconfig include/config/auto.conf:486:warning: symbol value 'elf32-i386' invalid for OUTPUT_FORMAT include/config/auto.conf:690:warning: symbol value 'arch/x86/configs/i386_defconfig' invalid for ARCH_DEFCONFIG include/config/auto.conf:896:warning: symbol value '' invalid for ACPI_CUSTOM_DSDT_FILE include/config/auto.conf:1692:warning: symbol value '-fcall-saved-ecx -fcall-saved-edx' invalid for ARCH_HWEIGHT_CFLAGS Getting required compilation flags failed. L4OBJ: /home/syslab1/l4fiasco/src/l4/build L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc /home/syslab1/l4fiasco/l4linux/arch/l4/Makefile:287: *** Aborting.. Stop. make: *** [sub-make] Error 2 Can anyone tell me where I am going wrong. This thing seems simple enough but i am sure i am making a simple mistake which i am unable to resolve. Will appreciate if someone can tell me how to make this error go away. Thanks Rahul

2 1

Building L4linux
by Maxime Lastera 05 Nov '10

05 Nov '10

Hi, A 'make' in /home/Maxx/Downloads/l4re/src/l4/mybuild come with successful end. In the directory /home/Maxx/Downloads/l4re/src/l4/mybuild/pc/ there are stdlibs.pc libio.pc l4re_c-util.pc and many more. -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

1 0

Building L4linux
by Maxime Lastera 04 Nov '10

04 Nov '10

Hi, The result of make in l4linux directory is : Getting required compilation flags failed. L4OBJ: /home/Maxx/Downloads/l4re/src/l4/mybuild L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc rtc /home/Maxx/Downloads/l4linux/arch/l4/Makefile:287: *** Aborting.. Stop. I understand these packages are not found, but when I check manually they are in L4tree directory, more precisely in l4re/src/l4/mybuild/pkg -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 1

Booting Fiasco with U-Boot (or: what is 0x002000000?)
by Thomas DuBuisson 03 Nov '10

03 Nov '10

All, Thanks for the previous help with building Fiasco/L4Re. Now that its built I have given a couple stabs at booting it on my beagleboard like device (I'll document all this in a blog and or wiki when/if I finish). Unfortunately I can't seem to get any sign of life on the screen (perhaps I should solder up a serial line for debugging purposes). What I've done: 1) Cross compiled L4Re and Fiasco for the beagleboard. 2) Copied l4re, lua, moe, fiasco, and created hello.lua to the SDs first partition (the fat boot partition). 3) Rebuilt/copied over u-boot.bin using: #define CONFIG_EXTRA_ENV_SETTINGS \ "bootargs=tbr=x console=tty1 omapfb.mode=dvi:1024x600MR-16@60 omapfb.vrfb=1 omapfb.vram=0:8M,1:4M,2:8M root=/dev/mmcblk0p2 rootdelay=1 rootfstype=ext3\0" #define CONFIG_BOOTCOMMAND \ "mmc init; fatload mmc 0 0x02000000 fiasco; bootm 0x02000000" Though I have tried different addresses including what I think is a typo on the "Getting Started" page of 0x002000000. So some questions are: 1) I'm pretty sure the bootargs need changed. For example, does u-boot need to load ned, moe, and hello? Where should they be loaded? Any other comments on what fiasco expects the bootloader to do? (this is different than what the wiki provides of "how to do those unspecified things using GRUB") 2) To what address should I load fiasco? I assume it matters. 3) If these questions are already answered somewhere then I'd be more than happy with a link. Cheers, Thomas

3 2

Building L4linux
by Maxime Lastera 03 Nov '10

03 Nov '10

When I set the L4 source directory to L4re build directory it's works, but some required L4 modules are required stdlibs log l4re_c-util libio shmc rtc. I have found this modules in the l4re-snapshot/src/l4/pkg but there are not found by the program. I need to copy the modules in an other directory ? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 1

Building L4linux
by Maxime Lastera 03 Nov '10

03 Nov '10

Hi, I have compiled fiasco and L4re with success. The Hello World exemple is running using qemu. Now I want to try L4linux on top of fiasco. When I try to comiple L4linux the following error occur: "cannot determine L4 source directory" The L4 source directory is the directory where I have built L4re or is a reference to an other directory ? -- ------------------------------------------------ Maxime LASTERA Phd Student

1 0

Information about buildingl4re
by Maxime Lastera 02 Nov '10

02 Nov '10

Hi, I try to add -fno-stack-protector-all to to GCCNOSTACKPROTOPT_f in l4/mk/ but I have always the same error. In a previou message "Fiasco / L4Re compilation issues" it said Fedora builds GCC with stack protection enabled. So if I understand, I have 2 solutions 1- build from source gcc on Fedora 2- install an other OS Do you have an other idea ? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 1

Information about buildingl4re
by Maxime Lastera 02 Nov '10

02 Nov '10

Hi, I want to test L4linux on top of L4/fisco I follow the building page of Fiasco, for this one all be done without error. So I start to follow the instructions to build L4re. I use the default configuration file. The results of the command "make O=path/to/builddir" failed because of an undefined reference to _stack_chk_fail_local. After some research I understand this "undefined reference" is add by gcc which is in version 4.4.4 on my fedora 13 OS. One soultion is to add CFLAGS= -fno-stack-protector in gcc command but I don't find gcc command in Makefile...! Do you have a solution ? Thanks in advance. -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

1 0

Fiasco / L4Re compilation issues
by Thomas DuBuisson 01 Nov '10

01 Nov '10

All, I've never had success with Fiasco but decided to give it another go so I could run some benchmarks. In short, I had one success and two failures. Any help would be appreciated. 1) I can build Fiasco for x86 on the host (32 bit x86 system). Yay 2) Can't build Fiasco for ARM on an x86 host due to... an old arm-linux-gcc version? 3) Can't build L4Re due to linker error. 1) Successful build of Fiasco x86 This and other builds are using a recent pull from the repo [1] on a Fedora based 32bit x86 system running gcc 4.4.4 on Linux 2.6.34. 2) Failure to build Fiasco ARM This early failure seems to be a simple problem with gcc changing the arguments - can anyone tell me the version of the "official" arm compiler in use? I'm running arm-linux-gcc 3.4.4. ------------ make[1]: Entering directory `/home/tommd/dev/L4/L4Re/build_arm' ... Generating version information ... Making kip.o cc1plus: error: invalid option `abi=apcs-gnu' make[1]: *** [kip.o] Error 1 ------------- 3) Failure to build L4Re due to linker error The symbol "__stack_chk_fail_local" is missing when building "libl4util.so" (see below). A quick objdump/grep doesn't show this symbol in any object file in the build directory - is the build system slightly broken? I see the source definition but don't really want to hack around in the build system. $ ld --version GNU ld version 2.20.51.0.2-20.fc13 20091009 ------------- make[5]: Entering directory `/home/tommd/dev/L4/L4Re/build/pkg/l4util/lib/src/OBJ-x86_core2-l4f' ==> Linking to shared libl4util.so /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `.L107': (.text+0xb79): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `.L358': (.text+0x1a85): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `_Unwind_Backtrace': (.text+0x24bf): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `_Unwind_ForcedUnwind': (.text+0x26ad): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `__frame_state_for': (.text+0x29e8): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o):(.text+0x2b78): more undefined references to `__stack_chk_fail_local' follow ld: libl4util.so: hidden symbol `__stack_chk_fail_local' isn't defined ld: final link failed: Nonrepresentable section on output make[5]: *** [libl4util.so] Error 1 ---------------- Cheers, Thomas [1] http://os.inf.tu-dresden.de/L4Re/download.html

4 5

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 November 2010