Re: [Tinycc-devel] 1cbb4d322bc3c89a3b56d35c803a19f99f33ab65 broke tcc on arm (RPi) 6 days ago
Try to revert ifeq ($(ARCH),arm) TARGET = arm - XCC = $(CC) else and test PS: arm-tcc can be a cross-compiler on x86. Can it compile arm *.S files in such case? ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
[Tinycc-devel] RE :Re: 1cbb4d322bc3c89a3b56d35c803a19f99f33ab65 broke tcc on arm (RPi) 6 days ago
This diff works too: nbsp; diff --git a/lib/Makefile b/lib/Makefile index 2288600..4293e69 100644 --- a/lib/Makefile +++ b/lib/Makefile @@ -84,7 +84,7 @@ else nbsp;ifeq $(TARGET) arm nbsp; OBJ = $(addprefix $(DIR)/,$(ARM_O)) nbsp; TGT = -DTCC_TARGET_ARM - XCC ?= $(TCC) -B$(TOP) + XCC ?= $(CC) nbsp;else nbsp;ifeq $(TARGET) arm64 nbsp; OBJ = $(addprefix $(DIR)/,$(ARM64_O)) gt; PS: arm-tcc can be a cross-compiler on x86. Can it compile arm *.S files in such case? nbsp; no idea - message d'origine - De : Sergey Korshunoff lt;sey...@gmail.comgt; date mar. 10/03/2015 11:24 (GMT +01:00) À : Christian JULLIEN lt;eli...@orange.frgt;, tinycc-devel@nongnu.org lt;tinycc-devel@nongnu.orggt; Objet : Re: [Tinycc-devel] 1cbb4d322bc3c89a3b56d35c803a19f99f33ab65 broke tcc on arm (RPi) 6 days ago Try to revert ifeq ($(ARCH),arm) TARGET = arm - XCC = $(CC) else and test PS: arm-tcc can be a cross-compiler on x86. Can it compile arm *.S files in such case? ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
[Tinycc-devel] 1cbb4d322bc3c89a3b56d35c803a19f99f33ab65 broke tcc on arm (RPi) 6 days ago
Hi all, nbsp; http://repo.or.cz/w/tinycc.git/blobdiff/7ed43415380ec6270e53c0ed3f42e5cb99df1f6e..1cbb4d322bc3c89a3b56d35c803a19f99f33ab65:/lib/Makefile nbsp; broke tcc on RPi. nbsp; tcc on arm is not able to compile assembler files On RPi, I use ./configure --with-libgc which used to select gcc to compile libtcc1.a After his change, it nownbsp;tries to use tcc instead of gcc which of course fails. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] 1cbb4d322bc3c89a3b56d35c803a19f99f33ab65 broke tcc on arm (RPi) 6 days ago
--with-libgcc means (tcc.h): library to use with CONFIG_USE_LIBGCC instead of libtcc1.a and not to select gcc to compile libtcc1.a. A solution for this problem: use gcc to compile asm files if target is arm-* PS: there is no such option as --with-libgc ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
[Tinycc-devel] RE :Re: 1cbb4d322bc3c89a3b56d35c803a19f99f33ab65 broke tcc on arm (RPi) 6 days ago
Thx Sergey, nbsp; Ok for wrong interpretation of --with-libgcc nbsp; I already fixed arm issue with: nbsp; diff --git a/lib/Makefile b/lib/Makefile index 2288600..e83d66f 100644 --- a/lib/Makefile +++ b/lib/Makefile @@ -84,7 +84,7 @@ else nbsp;ifeq $(TARGET) arm nbsp; OBJ = $(addprefix $(DIR)/,$(ARM_O)) nbsp; TGT = -DTCC_TARGET_ARM - XCC ?= $(TCC) -B$(TOP) + XCC = gcc -B$(TOP) nbsp;else nbsp;ifeq $(TARGET) arm64 nbsp; OBJ = $(addprefix $(DIR)/,$(ARM64_O)) I wonder if there is a better way to handle this? nbsp; C. - message d'origine - De : Sergey Korshunoff lt;sey...@gmail.comgt; date mar. 10/03/2015 11:07 (GMT +01:00) À : Christian JULLIEN lt;eli...@orange.frgt;, tinycc-devel@nongnu.org lt;tinycc-devel@nongnu.orggt; Objet : Re: [Tinycc-devel] 1cbb4d322bc3c89a3b56d35c803a19f99f33ab65 broke tcc on arm (RPi) 6 days ago --with-libgcc means (tcc.h): library to use with CONFIG_USE_LIBGCC instead of libtcc1.a and not to select gcc to compile libtcc1.a. A solution for this problem: use gcc to compile asm files if target is arm-* PS: there is no such option as --with-libgc ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Straightening out x86_64 build?
A crt*.o searching on Debian/Ubuntu is another problem. A problem you caused? A problem was caused by a Debians boys I think. In general, could you please be a bit more careful The same suggestion for debian boys. I only reverted a commit Set CONFIG_MULTIARCHDIR for cross compilers It was only debian oriented and breaks x86 / x86_64 compilres for linux other then debian. Correct me if I wrong. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Straightening out x86_64 build?
As a temporary solution making a symlinks to the /usr/lib/i386-*/* and /lib/i386-* can be used cd /lib ln -s i386-linux-gnu/* . cd /lib64 ln -s x86-64-linux-gnu/* . cd /usr/lib ln -s i386-linux-gnu/* . cd /usr/lib64 ln -s x86_64-linux-gnu/* . This will made a debian distro compatible with the other distros ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Straightening out x86_64 build?
A crt*.o searching on Debian/Ubuntu is another problem. A problem you caused? There is code in configure that looks for crti.o and sets CONFIG_MULTIARCHDIR. Why isn't it being used? In general, could you please be a bit more careful how you modify the build infrastructure if you're not able to test on the architectures affected by your changes? You can post a patch here if you're unsure. Thanks, Edmund ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] [PATCH] Convert some lines from ISO-8859-1 to UTF-8.
On March 9, 2015 7:16:40 AM GMT+08:00, Michael Matz matz@frakked.de wrote: Hi, On Sun, 8 Mar 2015, Edmund Grimley Evans wrote: Is this a good change, or pointless fiddling? It doesn't cause too much churn (only changes 10 lines), and it annoyed me sometimes as well, so IMHO it's a good change. Agreed. Best regards, Thomas ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
