[MacPorts] #56944: Error: Failed to build ld64-127: command execution failed

[MacPorts]

#56944: Error: Failed to build ld64-127: command execution failed
-----------------------+----------------------
  Reporter:  mrkapqa   |      Owner:  jeremyhu
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.5.3
Resolution:            |   Keywords:
      Port:  ld64-127  |
-----------------------+----------------------

Comment (by snunez1):

 I just went through the same process and can add a bit to this report. In
 addition to WaterFox, I sense that going forward long term maintenance is
 going to require a lot of self compiling, and having an update to date
 toolchain will really be welcome. Somethings, like Boost, require it. I am
 happy to help test. Fixing is probably beyond my abilities, but happy to
 help in any way I can.

 Here is what happened:

 After building clang 3.7 (step 4), I get this:
 {{{
 --->  Cleaning clang-3.7
 --->  Removing work directory for clang-3.7
 --->  Updating database of binaries
 --->  Scanning binaries for linking errors
 --->  No broken files found.
 ncurses is using libstdc++ (this installation is configured to use libc++)
 llvm-3.4 is using libstdc++ (this installation is configured to use
 libc++)
 ld64-127 is using libstdc++ (this installation is configured to use
 libc++)
 gettext is using libstdc++ (this installation is configured to use libc++)
 db48 is using libstdc++ (this installation is configured to use libc++)
 clang-3.4 is using libstdc++ (this installation is configured to use
 libc++)
 cctools is using libstdc++ (this installation is configured to use libc++)
 --->  Found 7 broken ports, determining rebuild order
 You can always run 'port rev-upgrade' again to fix errors.
 The following ports will be rebuilt:
  db48 @4.8.30+java
  ncurses @6.1
  gettext @0.19.8.1
  llvm-3.4 @3.4.2
  ld64-127 @127.2+llvm34
  clang-3.4 @3.4.2+analyzer
  cctools @895+llvm34
 Continue? [Y/n]:
 }}}
 Answered 'no' and continued with steps 5 and 6. After a long while:
 {{{
 ncurses is using libstdc++ (this installation is configured to use libc++)
 llvm-3.4 is using libstdc++ (this installation is configured to use
 libc++)
 ld64-127 is using libstdc++ (this installation is configured to use
 libc++)
 gettext is using libstdc++ (this installation is configured to use libc++)
 db48 is using libstdc++ (this installation is configured to use libc++)
 clang-3.4 is using libstdc++ (this installation is configured to use
 libc++)
 --->  Found 6 broken ports, determining rebuild order
 You can always run 'port rev-upgrade' again to fix errors.
 The following ports will be rebuilt:
  db48 @4.8.30+java
  ncurses @6.1
  gettext @0.19.8.1
  llvm-3.4 @3.4.2
  ld64-127 @127.2+llvm34
  clang-3.4 @3.4.2+analyzer
 Continue? [Y/n]:
 }}}
 Saying 'no' here and picking up with the rest of step 6 brings us right
 back to the error. Trying the rev-upgrade results in:
 {{{
 --->  Cleaning ncurses
 --->  Removing work directory for ncurses
 --->  Computing dependencies for llvm-3.4.
 --->  Cleaning llvm-3.4
 --->  Removing work directory for llvm-3.4
 Error: ld64: Variant llvm39 conflicts with llvm34
 Error: Unable to open port: Error evaluating variants
 Error: rev-upgrade failed: Error rebuilding ld64-127
 Error: Follow https://guide.macports.org/#project.tickets to report a bug.
 }}}
 I also tried 'yes' at the prompts and got the same errors.

-- 
Ticket URL: <https://trac.macports.org/ticket/56944#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS