<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">BTW, I am happy to make a binary available for you, if you need that.<div class=""><br class=""></div><div class="">I am considering putting up an entire archive site for Tiger PPC and Intel, and Leopard PPC and Intel, but I haven’t decided whether I want to take on the issues involved.</div><div class=""><br class=""></div><div class="">K<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 26, 2020, at 5:43 PM, Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com" class="">ken.cunningham.webuse@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote type="cite" class=""><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">However, I am stuck on PPC! I am unable to update MacPorts on my belowed
PowerMac since months - libgcc7 failure.
Compilation fails because stage2 and stage3 do not compile.
</pre></blockquote><br class=""><div class="">I will admit I do not as yet understand why this error happens sometimes.</div><div class=""><br class=""></div><div class="">You will see several tickets about this in trac with minimal searching, going back over the past 2 or 3 years.</div><div class=""><br class=""></div><div class="">Peter has this issue all the time on his PowerPC. I had never noticed this issue, until a recent build of gcc7 on a Tiger i386 system, when I got this too.</div><div class=""><br class=""></div><div class="">I am not certain if this is due to different dwarf debug symbols, but I can remember at one point we though this might be the issue.</div><div class=""><br class=""></div><div class="">I have wondered if the “compare” program was erring when doing the comparison.</div><div class=""><br class=""></div><div class="">Sometimes, for no particular reason, just restarting the gcc build again, without cleaning, can work.</div><div class=""><br class=""></div><div class="">There is a way to turn off the multiple-building-comparison feature, and just going straight to one bootstrap (stage1) and one final (stage2) compiler, and skip the stage3 comparison.</div><div class=""><br class=""></div><div class="">I don’t think you’d be taking much of a risk doing this — gcc is well-vetted.</div><div class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class="">Ken </div></div></div></blockquote></div><br class=""></div></body></html>