24-04-2020, 06:52 PM
(This post was last modified: 24-04-2020, 06:54 PM by josemendez.)
Quick update on the issue: Apple seems to be largely ignoring this:
![[Image: 7sFgEJk.png]](https://i.imgur.com/7sFgEJk.png)
It's been a month since I reported the bug, and their only answer (two weeks ago) was that we should disable bitcode generation as it "takes a long time to link". No difference though.
Since then I've tried disabling LTO, compiling the lib with symbol visibility hidden by default and manually exposing a few ones (in hopes that this would take pressure off the linker), stripping most symbols, tried to split the lib into 3 several smaller ones, disabled build parallelization, but no luck with any of these. Just in case someone wants to try the same: don't bother, it didn't work.
Will keep on investigating. Next idea I have in mind is performing a "bug binary search": deconstruct the entire lib to the bare minimum, see if the link process finishes, then slowly put it back together piece by piece until I find what's causing the linker to choke. Then, figure out if there's a way to work around it.
It's been a month since I reported the bug, and their only answer (two weeks ago) was that we should disable bitcode generation as it "takes a long time to link". No difference though.
Since then I've tried disabling LTO, compiling the lib with symbol visibility hidden by default and manually exposing a few ones (in hopes that this would take pressure off the linker), stripping most symbols, tried to split the lib into 3 several smaller ones, disabled build parallelization, but no luck with any of these. Just in case someone wants to try the same: don't bother, it didn't work.
Will keep on investigating. Next idea I have in mind is performing a "bug binary search": deconstruct the entire lib to the bare minimum, see if the link process finishes, then slowly put it back together piece by piece until I find what's causing the linker to choke. Then, figure out if there's a way to work around it.