Re: [Tinycc-devel] macOS Big Sur M1 port status

2021-02-25 Thread Michael Matz
chael. Le : 24 février 2021 à 18:24 (GMT +01:00) De : "Michael Matz" À : "jull...@eligis.com" , "tinycc-devel@nongnu.org" Objet : Re: [Tinycc-devel] macOS Big Sur M1 port status Hello, On Mon, 22 Feb 2021, Christian Jullien wro

Re: [Tinycc-devel] macOS Big Sur M1 port status

2021-02-24 Thread Christian JULLIEN
inycc-devel@nongnu.org" <tinycc-devel@nongnu.org> Objet : Re: [Tinycc-devel] macOS Big Sur M1 port status Hello, On Mon, 22 Feb 2021, Christian Jullien wrote: > I started to adapt mob to compile tcc natively on M1 (which is a damn > cool and fast CPU, really). > > With my

Re: [Tinycc-devel] macOS Big Sur M1 port status

2021-02-24 Thread Michael Matz
Hello, On Mon, 22 Feb 2021, Christian Jullien wrote: I started to adapt mob to compile tcc natively on M1 (which is a damn cool and fast CPU, really). With my few latest changes already pushed on mod, I’m able to build tcc and its libs. I’m facing an important issue with Big Sur, libc.dyli

[Tinycc-devel] macOS Big Sur M1 port status

2021-02-22 Thread Christian Jullien
Hi team, I started to adapt mob to compile tcc natively on M1 (which is a damn cool and fast CPU, really). With my few latest changes already pushed on mod, I'm able to build tcc and its libs. I'm facing an important issue with Big Sur, libc.dylib (or libc.a) no longer exist as file on dis