[MacPorts] #61243: libtool @2.4.6_9: link mode ignores specified compiler
MacPorts
noreply at macports.org
Thu Jun 22 04:07:52 UTC 2023
#61243: libtool @2.4.6_9: link mode ignores specified compiler
---------------------------+----------------------
Reporter: chrstphrchvz | Owner: larryv
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.6.3
Resolution: | Keywords:
Port: libtool |
---------------------------+----------------------
Comment (by ryandesign):
The libtermkey port is one that runs into this problem:
https://build.macports.org/builders/ports-10.6_x86_64-builder/builds/159291/steps
/install-port/logs/stdio
{{{
glibtool --quiet --mode=compile --tag=CC /opt/local/bin/clang-mp-11 -Os
-arch x86_64 -Wall -std=c99 -DHAVE_UNIBILIUM -o termkey.lo -c termkey.c
glibtool --quiet --mode=compile --tag=CC /opt/local/bin/clang-mp-11 -Os
-arch x86_64 -Wall -std=c99 -DHAVE_UNIBILIUM -o driver-csi.lo -c driver-
csi.c
glibtool --quiet --mode=compile --tag=CC /opt/local/bin/clang-mp-11 -Os
-arch x86_64 -Wall -std=c99 -DHAVE_UNIBILIUM -o driver-ti.lo -c driver-
ti.c
glibtool --quiet --mode=compile --tag=CC /opt/local/bin/clang-mp-11 -Os
-arch x86_64 -Wall -std=c99 -DHAVE_UNIBILIUM -o demo.lo -c demo.c
glibtool --quiet --mode=compile --tag=CC /opt/local/bin/clang-mp-11 -Os
-arch x86_64 -Wall -std=c99 -DHAVE_UNIBILIUM -o demo-async.lo -c demo-
async.c
glibtool --quiet --mode=link --tag=CC /opt/local/bin/clang-mp-11 -rpath
/opt/local/lib -version-info 15:2:14 -L/opt/local/lib
-Wl,-headerpad_max_install_names -arch x86_64 -L/opt/local/lib -lunibilium
-o libtermkey.la termkey.lo driver-csi.lo driver-ti.lo
/opt/local/bin/glibtool: line 10840: /opt/local/bin/clang-mp-3.7: No such
file or directory
make: *** [libtermkey.la] Error 127
}}}
If this is the correct syntax for telling libtool what compiler you want
it to use, then indeed it seems to be honoring it when compiling but
ignoring it when linking. I would want to fix that in libtool, not in each
individual port that uses libtool.
Christopher, you mentioned this is a long-known issue... do you know the
upstream bug report URL?
--
Ticket URL: <https://trac.macports.org/ticket/61243#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list