Sure, I always do ./configure.
I've just made a new test from a brand new checkout and error is gone.
For ARM32/64 I always do a clean checkout, I have the impression that failing
tests are new (and probably never tested before on RPi).
I'll try today or tomorrow to find the first commit that breaks tcc on RPi.
C.
Le : 09 février 2017 à 08:51 (GMT +01:00)
De : "grischka" <[email protected]>
À : "[email protected]" <[email protected]>
Objet : Re: [Tinycc-devel] Ready for Release 0.9.27
Christian Jullien wrote:
> *- Linux CentOS 6.x [KO]*
> ../tcc -B.. -I../include -I.. -I.. -DCONFIG_LDDIR="\"lib64\""
> -DTCC_TARGET_X86_64 ../tcc.c libtcc2 -lm -ldl -Wl,-rpath=. -o tcc2
>
> libtcc2:0: error: unrecognized character \x7f
Strange, should be libtcc2.so Seems DLLEXT=.so was not set from
configure. Did you ./configure?
> *- Raspberry Pi 3 (ARM) [KO]*
> ret_int_test... Makefile:226: recipe for target 'abitest' failed
> make[1]: *** [abitest] Segmentation fault
> Makefile:54: recipe for target '32_led.test' failed
> Makefile:54: recipe for target '42_function_pointer.test' failed
Are these regressions? If so we would probably need to know by
which commit it was introduced (I'm afraid)
> *- APM X-Gene Mustang board (Aarch64) [KO]*
>
> make[2]: *** [42_function_pointer.test] Error 1
Not sure about this 42_function_pointer.test. It's some new nifty
test for the linker.
Michael, is it supposed to work on ARM and/or AARCH64?
Thanks,
-- gr
_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
