<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class=""><br class=""></div><div class="">You have been told several times you need to clean the *failing* port, which is not xsane but libgcc.... Please run</div><div class=""><br class=""></div><div class="">> sudo port clean libgcc</div><div class="">> sudo port install libgcc</div><div class=""><br class=""></div><div class="">and then post the *complete* log you get…</div><div class=""><br class="">On 19 Mar 2016, at 5:03 pm, [ftp83plus] <<a href="mailto:gestos@ftp83plus.net" class="">gestos@ftp83plus.net</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">Hello all, </div><div class=""><br class=""></div><div class="">this is a log of failure of libgcc after cleaning xsane and trying to install it again:</div><div class=""><br class=""></div><div class=""><a href="http://pastebin.com/H0rQ7M03" class="">http://pastebin.com/H0rQ7M03</a></div><div class=""><br class=""></div><div class="">Any idea what would cause the failure?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div class=""><div class="">El 2016-03-17, a las 15:35, Ryan Schmidt escribió:</div><br class="Apple-interchange-newline"><blockquote type="cite" class=""><div class=""><br class="">On Mar 17, 2016, at 2:21 PM, [ftp83plus] <<a href="mailto:gestos@ftp83plus.net" class="">gestos@ftp83plus.net</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">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 class=""></blockquote><br class="">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 class=""><br class="">Segmentation faults leave behind crash logs in Library/Logs/DiagnosticReports which may provide further insight.<br class=""><br class=""><br class=""><blockquote type="cite" class="">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 class=""></blockquote><br class="">Let's be clear that at this point, xsane is not involved. The build failure is in libgcc.<br class=""><br class="">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 class=""><br class=""></div></blockquote></div><br class=""></div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">macports-users mailing list</span><br class=""><span class=""><a href="mailto:macports-users@lists.macosforge.org" class="">macports-users@lists.macosforge.org</a></span><br class=""><span class=""><a href="https://lists.macosforge.org/mailman/listinfo/macports-users" class="">https://lists.macosforge.org/mailman/listinfo/macports-users</a></span><br class=""></div></blockquote></body></html>