Hello Christian,
Thanks, nice to hear it went well! And on macOS 10.x tcc is probably still
picking up the .dylib files so nothing should break (the search order is
.dylib, then .tbd, then .a). The warnings are straightforward to fix and I will
do that soon, and push these changes to mob.
Going further,
Using native arm64 mon Big Sur M1, .o generated files are for ARM64
But after quickly patching arm64-link.c for case 9, it looks that binary is
for x86_64 see below:
jullien@mobley:~/tinycc $ ./tcc -c -B. ../foo.c -o foo.o
jullien@mobley:~/tinycc $ file foo.o
foo.o: ELF
Hi all, in case ...
a) you want to show your patches for people to comment or to test, but
b) do not (yet) want to commit on our main 'mob' branch', or, in general
c) your work is still "in progress" rather than ready to use, and
d) you look for a less tedious way than diffs attached to
With
./configure --cpu=x86_64
I can build a working tcc on macOS Big Sur M1.
Compiler works using Rosetta, generated code also produces x86_64 code which
runs the same way using Rosetta.
So your patch is workable solution to build and use tcc on macOS Big Sur M1
until the native port is fixed.
