gnu gcc builder script #686 #727
Conversation
|
Hmm. Instead of using our own gcc chain, we could also compile libgomp.a with spc. The only problem with this I see is that it would need to download the right version for the current compiler. |
|
And the second problem I see is that gcc is a massive download. And we need to download the full gcc tree to build libgomp (even though we don't need to build full gcc, just building libgomp is ok). |
|
It's doable that way, but I think using our own gcc toolchain, like we do for musl, is the better choice. that way we can explicitly support 1 compiler. |
|
It looks like we should add it to |
|
Yes, this has no place being in spc, it should be treated the same way as the musl toolchain. It would be nice if we could get gcc 15 to work instead, anyhow. I did compile it and successfully use it on my rhel 10 host, but had issues with >=11 in the centos 7 docker when I first tackled this. |
|
looking to switch to zig for better cross compilation instead |
What does this PR do?
#686