https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #202 from Sergey Fedorov <vital.had at gmail dot com> --- (In reply to Iain Sandoe from comment #187) > (In reply to Peter Dyballa from comment #186) > > ld: bl out of range (-16824316 max is +/-16M) from > > __ZSt21__throw_bad_exceptionv at 0x03AC2C7C in __text_cold of > > /opt/local/libexec/gcc10-bootstrap/lib/gcc/powerpc-apple-darwin9/10.5.0/../.. > > /../libstdc++.a(functexcept.o) to ___cxa_allocate_exception$island_2 at > > 0x02AB749C in __text of cc1 in __ZSt21__throw_bad_exceptionv from > > /opt/local/libexec/gcc10-bootstrap/lib/gcc/powerpc-apple-darwin9/10.5.0/../.. > > /../libstdc++.a(functexcept.o) > > collect2: error: ld returned 1 exit status > > make[3]: *** [cc1] Error 1 > > make[2]: *** [all-stage1-gcc] Error 2 > > make[1]: *** [stage1-bubble] Error 2 > > make: *** [all] Error 2 > This is caused by a bug in ld64 (there's a series of partial fixes and > work-arounds in various versions of ld64) ... I do have a fixed version but > that would mean you building some other code. > > I have some other things that need addressing - but will take a closer look > later (note that I do not see this issue in my build - and I am also using a > version of ld64 with the bug) . . I wonder if you are somehow pulling in a > different ld64 ... Iain, maybe suggest everyone use your tools, at least natively on powerpc on 10.5–10.6? (They do not work correctly in Rosetta, at least for me.) For ppc64 neither MacPorts nor Apple tools worked already for quite a while (we discussed that), and I have switched to using your xtools by default on 10.5–10.6. Admittedly, this adds complexity for someone building everything "by hand" from scratch, but even without gcc in picture, this ld64 issue will shoot out elsewhere sooner or later, so rather address its cause, IMO.
