pangox-compat configure failure

[saraanjum17]

Below is the output I get when I try to install Gwyddion:

--->  Computing dependencies for gwyddion
The following dependencies will be installed: 
 gtkglext
 libzip
 pangox-compat
 xorg-libXmu
 xorg-libXt
 xorg-libice
 xorg-libsm
Continue? [Y/n]: Y
--->  Fetching archive for pangox-compat
--->  Attempting to fetch pangox-compat-0.0.2_0.darwin_22.x86_64.tbz2 from https://packages.macports.org/pangox-compat
--->  Attempting to fetch pangox-compat-0.0.2_0.darwin_22.x86_64.tbz2 from http://mirror.fcix.net/macports/packages/pangox-compat
--->  Attempting to fetch pangox-compat-0.0.2_0.darwin_22.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/pangox-compat
--->  Configuring pangox-compat
Error: Failed to configure pangox-compat: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_pangox-compat/pangox-compat/work/pangox-compat-0.0.2/config.log
Error: Failed to configure pangox-compat: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_pangox-compat/pangox-compat/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port gwyddion failed

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log file.

[saraanjum17]

I'm not sure what the main.log file is or how to get it / access it. When I looked in my files, it found a handful of main.log files but none of them seemed related to the gwyddion installation attempt.

[ryandesign (Ryan Carsten Schmidt)]

The path of the main.log was given in your original bug report, as was the path of the config.log; please attach both of them:

Replying to saraanjum17:

Error: Failed to configure pangox-compat: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_pangox-compat/pangox-compat/work/pangox-compat-0.0.2/config.log

Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_x11_pangox-compat/pangox-compat/main.log for details.

[saraanjum17]

Oh thanks! I attached both of them.

[ryandesign (Ryan Carsten Schmidt)]

Thanks.

main.log says:

:info:configure configure: error: C compiler cannot create executables
:info:configure See `config.log' for more details

config.log says:

clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=13.0'

This means your clang is too old for macOS 13.

main.log says:

:debug:sysinfo macOS 13.3.1 (darwin/22.4.0) arch i386
:debug:sysinfo MacPorts 2.8.1
:debug:sysinfo Xcode none, CLT none

So as far as MacPorts knows, you have neither Xcode nor the Xcode command line tools (CLT) installed, yet you have clang, which would have been provided by one of those packages.

config.log says:

configure:2987: /usr/bin/clang --version >&5
Apple clang version 11.0.0 (clang-1100.0.33.17)

According to XcodeVersionInfo this is from Xcode or CLT 11.3.1, which is for macOS 10.14 and 10.15.

Probably, you were affected by the macOS bug that deleted the CLT receipt during macOS updates. The CLT receipt is what MacPorts reads to know what version of the CLT you have installed. The receipt is also what allows Software Update to know that you have something installed and to suggest updates for it. I think Apple has fixed the bug so the receipt won't be deleted again, but you'll need to reinstall the CLT one time to get the correct version installed, along with the receipt. See ProblemHotlist#reinstall-clt for instructions. In the future, Software Update should correctly suggest CLT updates for you.

Installing the current Xcode and/or CLT are part of the migration instructions. Since you missed this step, please review the other steps to ensure you followed them after you upgraded to macOS 13.

Once you get a compatible CLT installed, you'll still be unable to install pangox-compat because of #64228. Unfortunately I do not have a solution for that for you.