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 …
[View More]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
[View Less]
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 …
[View More]wondered can DDekit be used in L4Re?
If yes, how can I configure and compile the dde in /l4/pkg?
[View Less]
