<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hello all, </div><div><br></div><div>this is a log of failure of libgcc after cleaning xsane and trying to install it again:</div><div><br></div><div><a href="http://pastebin.com/H0rQ7M03">http://pastebin.com/H0rQ7M03</a></div><div><br></div><div>Any idea what would cause the failure?</div><div><br></div><div><br></div><div><br></div><br><div><div>El 2016-03-17, a las 15:35, Ryan Schmidt escribió:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>On Mar 17, 2016, at 2:21 PM, [ftp83plus] <<a href="mailto:gestos@ftp83plus.net">gestos@ftp83plus.net</a>> wrote:<br><br><blockquote type="cite">Indeed its is not a clean attempt as I tried many times. The first failure was a non-specific segmentation fault, so I restarted the process.<br></blockquote><br>Before reporting a problem, always clean and try again. An unclean build attempt can, in some cases, itself be the cause of a build failure.<br><br>Segmentation faults leave behind crash logs in Library/Logs/DiagnosticReports which may provide further insight.<br><br><br><blockquote type="cite">On my previous install of Macports, I didn't experience any issue installing xsane, but I didn't performed the libcxx update back then.<br></blockquote><br>Let's be clear that at this point, xsane is not involved. The build failure is in libgcc.<br><br>It's certainly possible that using libc++ instead of libstdc++ is contributing to the build failure; libc++ was, after all, not tested by most software developers on the OS you're using, and compiling a compiler is certainly a complicated proposition. However, at this point we don't know what's causing your build failure.<br><br></div></blockquote></div><br></body></html>