Nop! (I'll be away from CentOS until tomorrow morning)

Ok on RPi, broken on CentOS

gcc -o tcc.o -c tcc.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 -I.  
-Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
gcc -o libtcc.o -c libtcc.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 
-I.  -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
gcc -o tccpp.o -c tccpp.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 
-I.  -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
gcc -o tccgen.o -c tccgen.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 
-I.  -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
gcc -o tccelf.o -c tccelf.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 
-I.  -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
gcc -o tccasm.o -c tccasm.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 
-I.  -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
gcc -o tccrun.o -c tccrun.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 
-I.  -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
gcc -o x86_64-gen.o -c x86_64-gen.c -DCONFIG_LDDIR="\"lib64\"" 
-DTCC_TARGET_X86_64 -I.  -Wall -g -O2 -fno-strict-aliasing 
-Wno-pointer-sign -Wno-sign-compare -D_FORTIFY_SOURCE=0
gcc -o i386-asm.o -c i386-asm.c -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 
-I.  -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare 
-D_FORTIFY_SOURCE=0
ar rcs libtcc.a libtcc.o tccpp.o tccgen.o tccelf.o tccasm.o tccrun.o 
x86_64-gen.o i386-asm.o
gcc -o tcc tcc.o libtcc.a -lm -ldl -I.  -Wall -g -O2 -fno-strict-aliasing 
-Wno-pointer-sign -Wno-sign-compare -D_FORTIFY_SOURCE=0  
./texi2pod.pl tcc-doc.texi tcc.pod
pod2man --section=1 --center=" " --release=" " tcc.pod > tcc.1
texi2html -monolithic -number tcc-doc.texi
make: texi2html: Command not found
make: [tcc-doc.html] Error 127 (ignored)
makeinfo tcc-doc.texi
make: makeinfo: Command not found
make: [tcc-doc.info] Error 127 (ignored)
make -C tests test
make[1]: Entering directory `/home/cjullien/tinycc/tests'
------------ hello-exe ------------
../tcc -B.. ../examples/ex1.c -o hello || (../tcc -vv; exit 1) && 
./hello
/lib/libgcc_s.so.1: error: bad architecture
tcc version 0.9.25 (x86-64 Linux)
install: /usr/local/lib/tcc/
crt:
  /usr/lib64
libraries:
  /usr/lib64
  /lib64
  /usr/local/lib64
include:
  /usr/local/include
  /usr/include
  /usr/local/lib/tcc/include
elfinterp:
  /lib64/ld-linux-x86-64.so.2


With

[cjullien@hilbert ~]$ more tinycc/config.h 
/* Automatically generated by configure - do not modify */
#ifndef CONFIG_TCCDIR
# define CONFIG_TCCDIR "/usr/local/lib/tcc"
#endif
#define GCC_MAJOR 4
#define GCC_MINOR 4
#define HOST_X86_64 1
#define CONFIG_USE_LIBGCC
#define TCC_VERSION "0.9.25"



----- Message d'origine -----
De : "Thomas Preud'homme" <robo...@celest.fr>
Date jeu. 14/02/2013 18:06 (GMT +01:00)
À : "Christian JULLIEN" <eli...@orange.fr>
Cc : "tinycc-devel@nongnu.org" <tinycc-devel@nongnu.org>
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 >
> 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'
> 
> On CentOS

It should be good now.

Best regards,

Thomas
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to