libgcc fails to build

After cleaning libgcc and reinstalling, no error. Now attempting to install xsane…
Now webkit-gtk fails. I cleaned and reattempted installation, as told, but it failed again:
log is http://pastebin.com/wxyHSjBV



El 2016-03-19, a las 13:41, Chris Jones escribió:

> 
> You have been told several times you need to clean the *failing* port, which is not xsane but libgcc.... Please run
> 
> > sudo port clean libgcc
> > sudo port install libgcc
> 
> and then post the *complete* log you get…
> 
> On 19 Mar 2016, at 5:03 pm, [ftp83plus] <gestos at ftp83plus.net> wrote:
> 
>> Hello all, 
>> 
>> this is a log of failure of libgcc after cleaning xsane and trying to install it again:
>> 
>> http://pastebin.com/H0rQ7M03
>> 
>> Any idea what would cause the failure?
>> 
>> 
>> 
>> 
>> El 2016-03-17, a las 15:35, Ryan Schmidt escribió:
>> 
>>> 
>>> On Mar 17, 2016, at 2:21 PM, [ftp83plus] <gestos at ftp83plus.net> wrote:
>>> 
>>>> 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.
>>> 
>>> 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.
>>> 
>>> Segmentation faults leave behind crash logs in Library/Logs/DiagnosticReports which may provide further insight.
>>> 
>>> 
>>>> On my previous install of Macports, I didn't experience any issue installing xsane, but I didn't performed the libcxx update back then.
>>> 
>>> Let's be clear that at this point, xsane is not involved. The build failure is in libgcc.
>>> 
>>> 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.
>>> 
>> 
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20160321/94e5fd3c/attachment.html>