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

ftp83plus gestos at
Thu Jul 28 07:08:44 PDT 2016

The following ports are currently installed:
  cctools @877.5_2+llvm37
  cctools @877.8_0+llvm37
  cctools @886_1+llvm37 (active)
  ld64 @2_0+ld64_136 (active)
  ld64-136 @136_4+llvm37 (active)

El 2016-07-27, a las 22:40, Mihai Moldovan escribió:

> On 26.07.2016 02:13 PM, [ftp83plus] wrote:
>> I am currently attempting a "port selfupdate" operation before installing two
>> ports I'd like to test.
>> However, it fails for a reason I don't understand:
>> [...]
> Also interesting might be the output of
> `port installed 'ld64*' cctools`
> This problem might have been triggered by[0], although I have only seen proper
> linking failures on my system, not a segfaulting clang binary.
> Then again I'm natively on libc++ and a newer OS and Xcode version, so I can't
> rule out that clang might behave differently (or worse) on other systems.
> Regard this as additional information only though - a crashing clang binary
> should still be handled as well and reported upstream with the proper requested
> information.
> Mihai
> [0]

More information about the macports-users mailing list