Liviu Ionescu
Liviu Ionescu
> this is the section I was thinking of ... Thank you, I'll take a look. Now I'm rebuilding the development environments on all macOS versions to use the latest...
> hmm .. can you point me at the actual source used for the riscv toolchain ? Sure, here is the fork: - https://github.com/xpack-dev-tools/riscv-gcc/tree/v10.2.0-1.3
Ah, I forgot to mention, I also overwrite `config.sub` with: - https://github.com/xpack-dev-tools/build-helper/blob/master/config.sub
Hmmm... then how can we approach this issue? First to make the build pass, and then to minimise the risk?
> start with the backports branch I'm trying to digest this, but I don't know which branch you are referring to. In this repo I identified `gcc-10-3-extra-backports` and `gcc-10-coros-backports`. Then...
> those patches are on top of pristine 10.2 - you should be able to see that if you have a client that can view the trees. As graphical Git...
> I meant 11.2 ... I have not done the back ports to 10.x yet ah, ok, that explains it. so, for now I see no other way out than...
> the change to Darwin 20 was major did this happen between 10.2 and 10.3? is there a way to identify those commits?
> the time that the change occurred is not necessarily the important thing - it depends when/if fixes for it were back ported. I thought to use it as a...
I would also like to thank you for porting GCC to Apple Silicon, your project allowed me to start porting the [xPack Build Box](https://xpack.github.io/web-preview/xbb/) to Apple Silicon. Any plans to...