Except annoying new warnings reported on another thread, CentOS 6.3 x86_64 works using ./configure
----- Message d'origine ----- De : "Thomas Preud'homme" <robo...@celest.fr> Date ven. 15/02/2013 00:07 (GMT +01:00) À : "Christian JULLIEN" <eli...@orange.fr> Cc : "tinycc-devel@nongnu.org" <tinycc-devel@nongnu.org>, "grischka" <gris...@gmx.de> Objet : Re: [Tinycc-devel] test failure on Linux Le jeudi 14 février 2013 18:05:24, Christian JULLIEN a écrit : > This commit still works on RPi but produces > > ------------ test3 ------------ > ../tcc -B.. -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 -DONE_SOURCE > -run ../tcc.c -B.. -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 > -DONE_SOURCE -run ../tcc.c -B.. -DCONFIG_LDDIR="\"lib64\"" > -DTCC_TARGET_X86_64 -DONE_SOURCE -run ../tcc.c -B.. -run tcctest.c &gt; > test.out3 tcc: error: undefined symbol '__floatundixf' > tcc: error: undefined symbol '__va_start' > tcc: error: undefined symbol '__va_end' > make[1]: *** [test3] Error 255 > make[1]: Leaving directory `/home/cjullien/tinycc/tests' I thought I was testing with libgcc but I realized I wasn't. Testing with libgcc I can fully reproduce this bug. This seems to be symbols no longer exported by libgcc_s. For instance, __va_start is now defined to __builtin_va_start which is probably provided by gcc itself since I can't find it in libgcc_s. I guess it's the same for __floatundixf. I believe fixing it would take some time but I'm a bit annoyed that this doesn't work. Note though that tinycc would work most of the time, and the option of using libtcc1 remains. What's your opinion Grischka? Best regards, Thomas
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
