mpich-default: ld: unexpected token: !tapi-tbd-v3 file '/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib/libSystem.tbd' for architecture x86_64

[wz-billings (Zane Billings)]

I am trying to install octave using port. However, one of Octave's dependencies is mpich-default which I am not able to install. I am using MacOS Mojave 10.14.6 and Xcode 11.0.

I get the following error.

Error: Failed to configure mpich-default, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/work/mpich-3.3.1/config.log
Error: Failed to configure mpich-default: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port mpich-default failed

[wz-billings (Zane Billings)]

config.log file mentioned in error

[wz-billings (Zane Billings)]

main.log file mentioned in error

[eborisch (Eric A. Borisch)]

Can you try the resolution in this comment?

comment:ticket:58333:8

You want to clean/install mpich-default, not OpenBLAS, however.

[wz-billings (Zane Billings)]

Replying to eborisch:

Can you try the resolution in this comment?

​https://trac.macports.org/ticket/58333#comment:8

You want to clean/install mpich-default, not OpenBLAS, however.

This was the first thing I tried. I tried it again just to be safe and I got the same error.

[ryandesign (Ryan Carsten Schmidt)]

main.log says:

:info:configure checking whether Fortran 77 and C objects are compatible... no
:info:configure checking for file... file
:info:configure checking for linker for Fortran main program... configure: error: Could not determine a way to link a Fortran test program!

config.log says:

configure:42926: checking whether Fortran 77 and C objects are compatible
configure:43005: /usr/bin/clang -c  -pipe -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -arch x86_64   -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/work/mpich-3.3.1/src/mpl/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/work/mpich-3.3.1/src/mpl/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/work/mpich-3.3.1/src/openpa/src -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/work/mpich-3.3.1/src/openpa/src -D_REENTRANT -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_mpich/mpich-default/work/mpich-3.3.1/src/mpi/romio/include conftest.c >&5
configure:43005: $? = 0
configure:43008: mv conftest.o pac_conftest.o
configure:43011: $? = 0
configure:43020: /opt/local/bin/gfortran-mp-9 -o conftest  -pipe -m64 -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -arch x86_64 conftest.f pac_conftest.o  >&5
ld: unexpected token: !tapi-tbd-v3 file '/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/lib/libSystem.tbd' for architecture x86_64
collect2: error: ld returned 1 exit status

[eborisch (Eric A. Borisch)]

Is this still not working?

[kencu (Ken)]

this error happened due to the wrong linker being used.

the fix you referenced always works, because ld64 +xcode always works to handle tbd files on current systems.

this never had anything to do with mpich.

IMHO you can close this, and all similar tbd-related tickets. All have the exact same issue, and the same fix.

[wz-billings (Zane Billings)]

As I reported 17 months ago, the referenced fix did not work.

But I could not tell you if it works now, as approximately 16 months ago, I completely uninstalled macports and opted to install octave via homebrew, which solved the problem for me personally. As far as I am concerned this can be closed.

[kencu (Ken)]

thanks, Zane.

MacPorts has toolchain upgrade tech that homebrew never tried to implement. Occasionally, like this tbd issue, it trips up certain users.

Homebrew will be likely dropping your system soon, as because they cannot do any toolchain support, they can only support the last couple of systems.

When they drop you, we'll still be here! octave works 100% perfectly on MacPorts.