libxmi @1.2: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]

[pelopor-pelopor (pelopor)]

Build process stops at the "configure" stage.

:info:configure checking whether the C compiler (/usr/bin/clang -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX15.sdk -arch arm64 -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX15.sdk -arch arm64) works... no
:info:configure configure: error: installation or configuration problem: C compiler cannot create executables.
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_libxmi/libxmi/work/libxmi-1.2" && ./configure --prefix=/opt/local --infodir=/opt/local/share/info
:info:configure Exit code: 1

To build libxmi requires to use "autoreconf" rather than patches.

[pelopor-pelopor (pelopor)]

use autoreconf

[ryandesign (Ryan Carsten Schmidt)]

Why? What error did you get? Please attach the main.log file from the failed build attempt.

[pelopor-pelopor (pelopor)]

Just "configure" failed

[ryandesign (Ryan Carsten Schmidt)]

When configure fails, there is usually more information in configure's log, as mentioned in the main.log:

:error:configure Failed to configure libxmi: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_libxmi/libxmi/work/libxmi-1.2/config.log

Could you attach the config.log file as well?

[pelopor-pelopor (pelopor)]

OK, I attached config.log.

[ryandesign (Ryan Carsten Schmidt)]

The error in the config.log is:

configure:1070:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
 1070 | main(){return(0);}
      | ^
      | int
1 error generated.

This could be patched, like we do in many other ports, instead of using autoreconf. Does using autoreconf offer other advantages, beyond fixing this problem? Usually we try to avoid it unless patching is prohibitively difficult.