Hi,
On Fri Oct 29, 2010 at 12:09:52 -0700, Thomas DuBuisson wrote:
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.
- I can build Fiasco for x86 on the host (32 bit x86 system). Yay
- 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.
- 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.
Ok.
- 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
I'm mainly using the codesourcery ones nowadays (4.4). Nevertheless, does it help if you remove the abi=apcs-gnu line in src/Makeconf.arm?
- 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':
Could you do a 'make clean' and 'make V=1' and check whether a '-fno-stack-protector' is there somewhere on the gcc command line?
Thanks, Adam