clang 3.4 can't be configured (part of a selfupdate)

ftp83plus gestos at ftp83plus.net
Tue Jul 26 19:55:56 PDT 2016


What's the path to this log?

El 2016-07-26, a las 12:43, Ryan Schmidt escribió:

> 
>> On Jul 26, 2016, at 8:28 AM, [ftp83plus] <gestos at ftp83plus.net> wrote:
>> 
>> Here it is:
>> http://pastebin.com/3LRF0bDS
>> 
>> Mac OS X 10.6.8, MacBookPro8,1
> 
> 
> Ok, so according to that, MacPorts clang 3.7 is being used to try to configure MacPorts clang 3.4, but MacPorts clang 3.7 is crashing.
> 
> 
> configure:2188: checking for C compiler default output file name
> configure:2215: /opt/local/bin/clang-mp-3.7 -pipe -Os -arch x86_64 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 conftest.c  >&5
> clang: error: unable to execute command: Segmentation fault
> clang: error: clang frontend command failed due to signal (use -v to see invocation)
> clang version 3.7.1 (tags/RELEASE_371/final)
> Target: x86_64-apple-darwin10.8.0
> Thread model: posix
> clang: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
> 
> 
> Can you send us the crash log too? You may need to report this bug to the LLVM developers, as the error message says.
> 



More information about the macports-users mailing list