I'll try later this afternoon to update my own gtk3 on the same system and let you know what happens.
Looks like it might be just your ld64* port that is dysfunctional - I suppose we could make up an example that tests the linker, like we did for clang, and see if that segfaults. Sorry I don't have time to create that right now. I don't know if you can just uninstall and then reinstall ld64 to "short version" the reinstall of what appears to be the faulty executable. I would probably try to see if I could do that, myself. I suspect the dependencies might prevent that. I think ultimately you're into the reinstall of the tool chain that I described previously to fix the segfaulting ld64. Having these as binaries that you could install rather than the 6 hour compiling process would make it less painful. I usually run it overnight (the clang and llvm parts take all the time). I know you have to "build from source" for this system at present (lots of talk about the buildbot coming soon, though). You are coming through some 'real-world' issues that are helpful to figure out any inconsistencies in the system. I hope this helps, Ken On 2016-08-28, at 1:44 AM, Ryan Schmidt wrote: > On Aug 27, 2016, at 12:41, [ftp83plus] <ges...@ftp83plus.net> wrote: >> >> So, after reinstalling Mac OS X as I did to get out of the startup crash as >> I did, even if ports stayed in place, I should re-perform the >> LibcxxOnOlderSystems steps? > > In general, no, reinstalling the same version of macOS does not necessitate > reinstalling MacPorts and your ports. However, the issues Mihai noted may > require reinstalling the affected ports. I'm not an expert at reading crash > logs so I can't say for certain why your crash occurred. I just know that > when a crash occurs, you should provide the crash log so that someone who is > more familiar might be able to help. > > > >>> El 2016-08-27, a las 12:17, Mihai Moldovan escribió: >>> >>>> On 27.08.2016 04:00 PM, [ftp83plus] wrote: >>>> Crash log, approximately when gtk3 segfaulted: >>>> >>>> http://pastebin.com/bzuez8Xp >>> >>> In there, I see two things that look weird: >>> >>> - you're using ld64-136, although step 8 and 9 of the LibcxxOnOlderSystems >>> guide explicitly says to switch to ld64-latest >>> - ld64-136 was installed with +llvm37, although step 5 and 7 make sure that >>> +llvm38 is used >>> >>> The second problem may be explicable by upgrading - earlier versions >>> probably >>> used llvm37 and the llvm38 change is relatively new. >>> >>> Still, your setup is broken/deviates from what is advertised to work on >>> 10.6. >>> That crash is probably a consequence of that. > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
