l4-hackers

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

2827 discussions

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

How to compile DDekit in l4re-snapshot-2010080920?
by 方明伟 25 Oct '10

25 Oct '10

Hi : Everyone! I am a new one to use fiasco.OC. Now, I am compiling L4Linux for X86 and arm. But I didn't know how to configure the DDekit. In "l4/pkg/dde/Makefile", three senteces are being commented. "# $(VERBOSE)PWD=$(PWD)/linux26/include $(MAKE) -C linux26/include # $(VERBOSE)PWD=$(PWD)/linux26/contrib/include $(MAKE) -C linux26/contrib/include" "# $(VERBOSE)PWD=$(PWD)/linux26/lib $(MAKE) -C linux26/lib" Does that mean I can't use the DDekit now? So I wondered can DDekit be used in L4Re? If yes, how can I configure and compile the dde in /l4/pkg?

2 1

L4Re multiple Linux instances communication
by Michael Weiß 27 Sep '10

27 Sep '10

Hi, I'm trying to establish a communication between several L4Linux instances on fiasco.oc kernel with L4Re on the beagle board, preferable through a virtual network. I found out that the outdated L4env provided a virtual netwok switch, ORe and the l4ore driver in L4Linux for that purpose. Is there something similar available for L4Re and how can I setup a connection between two L4Linux instances? Thanks, Michael

2 8

Re: L4 and ARM Cortex-A8 (OMAP3)
by Brett Mahar 22 Sep '10

22 Sep '10

> Fiasco.OC/L4Re supports the beagleboard out of the box now, at least the > older versions. I'm not sure about the XM, I hope it's not completely > different to the previous ones. > Adam That is good news. The xM uses DM3730 main chip, which is supposedly "compatible with OMAP-3 architecture." Both chips built around cortex-A8 core, so hopefully all will be well. Brett.

1 0

Re: L4 and ARM Cortex-A8 (OMAP3) Thomas DuBuisson
by Brett Mahar 22 Sep '10

22 Sep '10

On Thu Apr 22, 2010 at 15:37:55 -0700, Thomas DuBuisson wrote: > I'm wanting to experiment with L4 on a OMAP3 (beagleboard based) > system but am having difficulting finding a suitable L4 microkernel. > Does anyone on this list have comments/suggestions wrt which kernel to > use, building, u-boot configuration, etc? >>I don't want to promise too much but I have a Fiasco version for the BB >>sitting on my disk. I'm currently trying to get all this in a reasonable >>state. >>Adam Just wondering if anyone has got any new info since these posts earlier in the year? I am waiting on a beagleboard xm to arrive in the mail.... Brett.

2 1

how to run Fiasco.OC
by 方明伟 16 Sep '10

16 Sep '10

2 1

Hello World!
by Marc Mauri Alloza 10 Sep '10

10 Sep '10

Hello I'm new to L4, L4re and all this stuff and i'm trying to find the jdb manual, most links I found in internet are broken. Someone knows how to find it? Thanks.

2 1

Debugging applications on Fiasco.OC. and questions about L4re
by Pablo Montesinos 01 Sep '10

01 Sep '10

(sorry if it's a duplicate, I sent the previous one from an account outside the mailing list and I did not know whether it would go through) Hi, I need to debug an application that I've ported to Fiasco.OC and I was wondering what is the preferred way to do it. (The application works fine in Linux, but there must be something wrong with the libraries I ported). Jdb seems not very friendly if all you want to do is debugging an application. My second question is about L4re. So far, all the applications running on my Fiasco.OC are console-based. However, I would like to run more complex apps that might require a graphical environment. I noticed that, with L4env, it was possible to have it. Is it possible to do it with L4re? Any plans to add it in the near future. I would use Genode, but I've been told at the Genode list that Fiasco.OC is not supported by Genode. Is there an alternative to Genode on L4re? Thanks, Pablo

2 3

Fiasco.OC hangs in Intel Core 2 duo
by Karthik Vadambacheri Manian 29 Aug '10

29 Aug '10

Hi all, I compiled the new Fiasco.OC microkernel and L4RE in my Core 2 Duo PC with gcc 4.4.3. While configuring the Fiasco.OC microkernel I selected PC architecture as AMD64 and CPU type as Intel Core 2. But while configuring L4RE when I selected the PC architecture as AMD64 there is no option for CPU type as Intel Core 2. Hence I selected PC type as K8 which is one of the options. I created the cd image using *make grub2iso E=hello. *But when I run the virtual machine in qemu-system-x86_64 it hangs. I have tested the same with different PC type as K10/Barcelona, opteron, but got the same result. I have pasted the output below: ========================================================= $ qemu-system-x86_64 -m 1024m -cdrom hello.iso -boot d -serial stdio Welcome to Fiasco.OC (amd64)! L4/Fiasco.OC amd64 microkernel (C) 1998-2010 TU Dresden Rev: r16 compiled with gcc 4.4.3 for Intel Core2 [] Build: #1 Tue Aug 17 12:12:24 EDT 2010 Performance-critical config option(s) detected: CONFIG_NDEBUG is off Superpages: yes Kmem:: cpu page at 3fde6000 (4096Bytes) ACPI-Init ACPI: RSDP = 0xf8960 pRSDT = 3fffde30 pXSDT = 0 ACPI: OEM: BOCHS MADT = 0x201fdeb0 IO-APIC: struct: 0x201fdee4 adr=fec00000 IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 IO-APIC: ovr[ 1] 05 -> 5 IO-APIC: ovr[ 2] 09 -> 9 IO-APIC: ovr[ 3] 0a -> a IO-APIC: ovr[ 4] 0b -> b IO-APIC: NOTE IRQ overrides are ignored! IO-APIC: pins 23 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) Allocate cpu_mem @ 0xfffffffffffe9000 Local APIC[00]: version=14 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the PIT (i8254) on IRQ 2 for scheduling CPU[0]: GenuineIntel (6:2:3:0) Model: Unknown CPU at 2397 MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 32768 bytes (8 pages) Calibrating timer loop... ======================================================== Also while creating image using *make grub2iso E=hello*, the fiasco microkernel could not be located by the make script. It said the following error. $ make grub2iso E=hello make[1]: Entering directory `/home/karthik/Research/tudos/src/l4' Processing entry 'hello' Could not find 'fiasco' with path ':/home/karthik/Research/tudos/src/ubuild/bin/amd64_K8:/home/karthik/Research/tudos/src/ubuild/bin/amd64_K8/l4f:/home/karthik/Research/tudos/src/ubuild/lib/amd64_K8:/home/karthik/Research/tudos/src/ubuild/lib/amd64_K8/l4f' at tool/lib/L4/ModList.pm line 271. But when I made a symbolic link to the fiasco microkernel built previously to one of the directories in the above path, it got resolved. It would be great if it could find the microkernel by itself. Please let me know how to overcome the above issues. Thanks a lot for your time, karthik

3 3

Jump to page:

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