On 6/2/07, Lev Shamardin <[EMAIL PROTECTED]> wrote:
Statically linked eggs are just fine for me, because I do not have dynamic loading support on the target platform. The problem is still there. I try to configure like this: export TARGET_PREFIX=/home/dev/cross-chicken/install export TARGET_CC="m68k-elf-gcc -m68000" export TARGET_CFLAGS="-Os -g -fomit-frame-pointer -m68000 -DCONFIG_LINEO -Dlinux -D__linux__ -Dunix -D__uClinux__ -DEMBED -D__USE_BSD -fno-builtin -msep-data" export TARGET_LDFLAGS="$TARGET_CFLAGS -Wl,-elf2flt -Wl,-move-rodata -nostartfiles" export TARGET_LIBS="-lc" export CFLAGS=$TARGET_CFLAGS export LDFLAGS=$TARGET_LDFLAGS export LIBS=$TARGET_LIBS export TARGET_CXX="m68k-elf-g++ -m68000" export TARGET_RUN_PATH=/usr ./chicken-2.613/configure --without-libffi --prefix=/home/dev/cross-chicken/install --build=i686-linux --host=m68k-elf --disable-shared
Note that this is incorrect: the first (68k-native) chicken should be built without the TARGET_... variables. Not that this will change anything with the actual compilation problem, though... What gcc version are you using? It first bails out in runtime.c, right? I have successfully compiled the runtime system for a Dragonfire 68k-based system before (but didn't get it to run yet), so perhaps this is a gcc bug. cheers, felix _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
