tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tinycc-devel] RE :Re: test failure on Linux


From: Christian JULLIEN
Subject: [Tinycc-devel] RE :Re: test failure on Linux
Date: Fri, 15 Feb 2013 09:13:26 +0100 (CET)

Except annoying new warnings reported on another thread, CentOS 6.3 x86_64 works using ./configure


----- Message d'origine -----
De : "Thomas Preud'homme" <address@hidden>
Date ven. 15/02/2013 00:07 (GMT +01:00)
À : "Christian JULLIEN" <address@hidden>
Cc : "address@hidden" <address@hidden>, "grischka" <address@hidden>
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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]