[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 Iain Sandoe changed: What|Removed |Added Build|x86_64-apple-darwin1[5678] |x86_64-apple-darwin1[56789] ||, *-apple-darwin2* --- Comment #6 from Iain Sandoe --- fixed on trunk using the @rpath mechanism; TODO - determine if this might reasonably be back-ported.
[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 Richard Biener changed: What|Removed |Added Target Milestone|10.5|---
[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 Jakub Jelinek changed: What|Removed |Added Target Milestone|10.4|10.5 --- Comment #5 from Jakub Jelinek --- GCC 10.4 is being released, retargeting bugs to GCC 10.5.
[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 --- Comment #4 from Iain Sandoe --- (In reply to Iain Sandoe from comment #0) > Possible fix #1 > === > > This is what I've been tinkering with > > 1) convert all the target libraries to use @rpath/libx.dylib as their > install names > 2) get GCC to emit the necessary rpaths into executables during build and > test (and, obviously, at install time). > > Actually, this is sensibly in line with a useful macOS deployment model - > since the "approved" way to package shared libraries on macOS / Darwin is to > place them alongside the executables and use rpaths. > > unfortunately: > * it's quite an involved set of changes and almost certainly not going to > happen for 9. > * there are details to work out to make sure that build-time paths don't > leak into installed libraries/exes. tested and working fix posted here: https://gcc.gnu.org/pipermail/gcc-patches/2021-November/584775.html > Possible fix #2 > === > > Have a build environment where all the used executables and paths are > outside the remit of SIP. This is untested so far, and might not suit the > casual user of GCC - since it would involve building at least a shell / make > / GCC prerequisites etc. Not going to work - /bin/sh is hardwired into configure scripts.
[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 Richard Biener changed: What|Removed |Added Target Milestone|10.3|10.4 --- Comment #3 from Richard Biener --- GCC 10.3 is being released, retargeting bugs to GCC 10.4.
[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 Richard Biener changed: What|Removed |Added Target Milestone|10.2|10.3 --- Comment #2 from Richard Biener --- GCC 10.2 is released, adjusting target milestone.
[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 Jakub Jelinek changed: What|Removed |Added Target Milestone|10.0|10.2 --- Comment #1 from Jakub Jelinek --- GCC 10.1 has been released.
[Bug bootstrap/88590] System Integrity Protection (SIP) breaks GCC build assumptions on Darwin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88590 Iain Sandoe changed: What|Removed |Added Keywords||build Status|UNCONFIRMED |NEW Last reconfirmed||2018-12-24 Target Milestone|--- |10.0 Ever confirmed|0 |1 Build||x86_64-apple-darwin1[5678]
