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

[MacPorts]

#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 Schamschula):

 I've looked at my local install (Sonoma/arm64). I get

 {{{
 % otool -L /opt/local/bin/octave
 /opt/local/bin/octave:
 /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
 (compatibility version 150.0.0, current version 2420.0.0)
 /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
 (compatibility version 1.0.0, current version 1226.0.0)
         /opt/local/lib/libreadline.8.dylib (compatibility version 8.2.0,
 current version 8.2.0)
         /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
 (compatibility version 2.0.0, current version 170.0.0)
         /opt/local/lib/libiconv.2.dylib (compatibility version 9.0.0,
 current version 9.1.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 1345.100.2)
         /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current
 version 1700.255.0)
 /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
 (compatibility version 64.0.0, current version 1774.4.3)
 }}}

 {{{
 % mkoctfile -p ALL_LDFLAGS
  -fPIC -L/opt/local/lib/octave/9.2.0 -L/opt/local/lib -bundle -undefined
 dynamic_lookup -bind_at_load -bundle_loader /opt/local/bin/octave-9.2.0
 }}}

 and

 {{{
  % otool -L /opt/local/share/octave/packages/piqp-0.4.1/piqp_oct.oct
 /opt/local/share/octave/packages/piqp-0.4.1/piqp_oct.oct:
         /opt/local/lib/octave/9.x.x/liboctinterp.dylib (compatibility
 version 13.0.0, current version 13.1.0)
         /opt/local/lib/octave/9.x.x/liboctave.dylib (compatibility version
 12.0.0, current version 12.1.0)
         /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current
 version 1700.255.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 1345.100.2)
 }}}

 However,

 {{{
 % mkoctfile -p CC
 /usr/bin/clang
 }}}

 and

 {{{
 % mkoctfile -p CXX
 /usr/bin/clang++ -std=gnu++11
 }}}

 So octave packages are expected to use the Xcode compilers, unless the
 package needs Fortran, e.g. {{{octave-control}}}, or specifies a
 particular version of clang, e.g. {{{octave-molsim}}}.

 The {{{octave}}} PortGroup is a little different. It is supposed to
 compile everything in the configure phase. The build phase does nothing.
 However, I agree that no compiling should happen in the destroot phase,
 but it happens all the time for aqua, i.e. Xcode,  ports.

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