Re: [Tinycc-devel] Major issue with current macos port. clang and tcc .o are not compatible

[Christian Jullien]

Sure that's also what I do on the different Linux that support tcc (x86,
x86_64, arm, aarch64, riscv).
On macos it does not work because it fails when trying to "ar *.o" as .o are
not MACH-O but ELF. macOS version of ar silently drop them.
To work, you have to adapt configure.ac to use "tcc -ar" instead of ar *AND*
no longer call ranlib.

C.

-----Original Message-----
From: arnold@skeeve.com [mailto:arnold@skeeve.com] 
Sent: Wednesday, June 24, 2020 16:29
To: tinycc-devel@nongnu.org; jullien@eligis.com
Subject: Re: [Tinycc-devel] Major issue with current macos port. clang and
tcc .o are not compatible

"Christian Jullien" <eligis@orange.fr> wrote:

> I think that what annoys me the most is that standard ar and ranlib
commands do not work with tcc generated .o files.
> For sure, I can drop ranlib calls and replace ar by "tcc -ar rcs" but this
must be done in every configure.ac and standard .m4 you have or use.
> It means that you probably won't be able to use any open source package
with "CC=tcc ./configure".

I build gawk that way on Linux all the time, for years. Including the
static libray of support routines. So, are you sure?

Arnold