<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><br><div><div><div>El 2016-07-27, a las 01:43, Jeremy Huddleston Sequoia escribió:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><blockquote type="cite">On Jul 26, 2016, at 19:58, Ryan Schmidt &lt;<a href="mailto:ryandesign@macports.org">ryandesign@macports.org</a>&gt; wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jul 26, 2016, at 9:55 PM, [ftp83plus] wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">El 2016-07-26, a las 12:43, Ryan Schmidt escribió:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On Jul 26, 2016, at 8:28 AM, [ftp83plus] wrote:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Here it is:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://pastebin.com/3LRF0bDS">http://pastebin.com/3LRF0bDS</a><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Mac OS X 10.6.8, MacBookPro8,1<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">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.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">configure:2188: checking for C compiler default output file name<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">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 &nbsp;&gt;&amp;5<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">clang: error: unable to execute command: Segmentation fault<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">clang: error: clang frontend command failed due to signal (use -v to see invocation)<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">clang version 3.7.1 (tags/RELEASE_371/final)<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Target: x86_64-apple-darwin10.8.0<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thread model: posix<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">clang: note: diagnostic msg: PLEASE submit a bug report to <a href="http://llvm.org/bugs/">http://llvm.org/bugs/</a> and include the crash backtrace, preprocessed source, and associated run script.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Can you send us the crash log too? You may need to report this bug to the LLVM developers, as the error message says.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">What's the path to this log?<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">It would be in Library/Logs/DiagnosticReports. I'm not sure which Library folder. Maybe the main /Library folder?<br></blockquote><br>Probably /Library/Logs/DiagnosticReports. &nbsp;If unsure, look in syslog (/var/log/system.log*) as it'll contain a log line which points you to the crash log.<br></div></blockquote><br></div></div><div>Indeed it was in that path.</div><div><br></div><div>Pastebin link:&nbsp;<a href="http://pastebin.com/KvyHmTBB">http://pastebin.com/KvyHmTBB</a></div></body></html>