[MacPorts] #70277: octave-piqp @0.4.1: sh: /opt/local/bin/clang++-mp-16: No such file or directory

MacPorts noreply at macports.org
Mon Jun 24 00:39:14 UTC 2024


#70277: octave-piqp @0.4.1: sh: /opt/local/bin/clang++-mp-16: No such file or
directory
--------------------------+-------------------------
  Reporter:  ryandesign   |      Owner:  Schamschula
      Type:  defect       |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.9.3
Resolution:               |   Keywords:
      Port:  octave-piqp  |
--------------------------+-------------------------

Comment (by ryandesign):

 gcc13-libcxx has a ''build'' dependency on clang-16, so clang-16 is only
 guaranteed to be present when building gcc13-libcxx. It is not guaranteed
 to be present when gcc13-libcxx is later used. If gcc13-libcxx has that
 requirement then clang-16 needs to be changed to a ''library'' dependency.
 But I do not find any occurrences of "clang++-mp-16" in the files
 installed by the gcc13-libcxx port so I do not think such a change is
 necessary or appropriate.

 This is a case of octave-piqp, and possibly all ports that use octave, not
 UsingTheRightCompiler. The log shows `DEBUG: Using compiler 'Xcode Clang'`
 and `CXX='/usr/bin/clang++'` and yet a different compiler was used; that
 is the bug. Additionally, it was trying to use this compiler during the
 destroot phase; compiling should happen during the build phase.

 Downloading the 10.11 binary for octave from the private server, I see
 that the files /opt/local/bin/mkoctfile-9.2.0,
 /opt/local/lib/octave/9.2.0/liboctinterp.12.dylib, and
 /opt/local/lib/octave/9.2.0/liboctinterp.a all contain the string
 `/opt/local/bin/clang++-mp-16`. Perhaps octave is trying to use that
 compiler when compiling octave-piqp and possibly other modules, and needs
 to be told (by the port or the portgroup) not to do that. It needs to use
 the compiler MacPorts specifies.

 If /usr/bin/clang++ is not usable for compiling octave-piqp and other
 octave modules, then the normal MacPorts compiler selection mechanisms
 need to be used to tell MacPorts to select a suitable compiler.

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


More information about the macports-tickets mailing list