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. Once you fixed the warnings I'll love to see this patch in mod (if maintainers agree). C. -----Original Message----- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Sushant Pandurangi Sent: Monday, July 05, 2021 10:03 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Linking system dylibs on macOS 11+ 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. Never touched an M1 yet so I had no idea what to expect, but I had forgotten about Rosetta, so that's an option for now. As for arm64 codegen/link, sadly I am not at all familiar with that part of the code to be able to help as yet. Regards, Sushant _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
