mumps @5.6.2_0+gfortran+mpich+openblas: ld: unknown options: -commons

[murrayE]

This is even when using Xcode 15.1 Beta. There are *many* warnings during build about mismatched types and ranks . But perhaps crux of the failure is this, from near end of the main.log:

:info:build make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_mumps/mumps/work/MUMPS_5.6.2/PORD/lib'
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_mumps/mumps/work/compwrap/cc/opt/local/bin/mpicc-mpich-mp -dynamiclib -install_name /opt/local/lib/libpord.dylib graph.o gbipart.o gbisect.o ddcreate.o ddbisect.o nestdiss.o multisector.o gelim.o bucket.o tree.o symbfac.o interface.o sort.o minpriority.o  -o libpord.dylib
:info:build ld: unknown options: -commons 
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)
:info:build make[1]: *** [libpord.dylib] Error 1

[murrayE]

main.log

[catap (Kirill A. Korinsky)]

murrayE, unfortunately I haven't got Sonoma to test a fix. But if you can help me by edit a port file via port edit mumps and adding somewhere after -fPIC a line: configure.ldflags-append -Wl,-ld_classic.

[Dave-Allured (Dave Allured)]

I checked source code and port files for Mumps 5.6.2. -commons is not specified or needed anywhere by Mumps, because Mumps does not use fortran COMMON or EQUIVALENCE anywhere. (Reference: Xcode docs for "ld".)

Meanwhile, it looks like -commons is being injected here from /opt/local/bin/mpicc-mpich-mp. -commons is a known problem with the Sonoma/Xcode 15.0 linker. So check mpicc-mpich for -commons problems. It is possible that there is already an open ticket for this. That is all I have time for right now.

Oh yeah, I agree that @catap's -ld_classic suggestion may be a viable temporary workaround. That is also tricky because the previous linker will choke if it gets that flag unintentionally.

[catap (Kirill A. Korinsky)]

Replying to Dave-Allured:

Meanwhile, it looks like -commons is being injected here from /opt/local/bin/mpicc-mpich-mp. -commons is a known problem with the Sonoma/Xcode 15.0 linker. So check mpicc-mpich for -commons problems. It is possible that there is already an open ticket for this. That is all I have time for right now.

So, this means that as soon as mpich is updated, it should be fixed as well

[Dave-Allured (Dave Allured)]

Replying to catap:

So, this means that as soon as mpich is updated, it should be fixed as well

Yes I expect so. Alternatively if the upcoming Xcode 15.1 linker fixes -commons, that should also fix this. However, given the complete lack of intelligence about -commons in Apple's various Xcode release notes, I do not hold out much hope for that.

[kencu (Ken)]

duplicate of #68346, which is tracking the issue with -commons

[Dave-Allured (Dave Allured)]

In 93643f6fd1e7d732f2c866117cc1f4939c564a0e/macports-ports (master):

mumps @5.6.2: Doc fix only, home page

.

CI expected fail due to:
#68691

Allow CI to run anyway, to confirm that URL change does not break distfile fetches.