Error: Failed to configure doxygen: configure failure: command execution failed

[forrie (Forrest)]

After upgrading my system to Monterey and Macports to 2.7.1, my port update is failing with this error:

--->  Updating MacPorts base sources using rsync
MacPorts base version 2.7.1 installed,
MacPorts base version 2.7.1 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
Warning: The macOS 12 SDK does not appear to be installed. Ports may not build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by running `xcode-select --install'.
--->  Computing dependencies for doxygen
--->  Fetching archive for doxygen
--->  Attempting to fetch doxygen-1.9.2_0.darwin_21.x86_64.tbz2 from https://packages.macports.org/doxygen
--->  Attempting to fetch doxygen-1.9.2_0.darwin_21.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/doxygen
--->  Attempting to fetch doxygen-1.9.2_0.darwin_21.x86_64.tbz2 from https://mse.uk.packages.macports.org/doxygen
--->  Fetching distfiles for doxygen
--->  Verifying checksums for doxygen
--->  Extracting doxygen
--->  Applying patches to doxygen
--->  Configuring doxygen
Error: Failed to configure doxygen: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/main.log for details.
Error: Problem while installing doxygen
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.

root@MacbookPro ➜  src port installed | grep -i doxygen

I've performed a port clean, I uninstalled doxygen -- as you can see, the installed list doesn't show it in the local system.

The last part of the referenced log file possibly identifies the issue:

:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.9.2" && /opt/local/bin/cmake -G "CodeBlocks - Unix Makefiles" -DCMAKE_BUILD_TYPE=MacPorts -DCMAKE_INSTALL_PREFIX="/opt/local" -DCMAKE_INSTALL_NAME_DIR="/opt/local/lib" -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DCMAKE_C_COMPILER="$CC" -DCMAKE_CXX_COMPILER="$CXX" -DCMAKE_OBJC_COMPILER="$CC" -DCMAKE_OBJCXX_COMPILER="$CXX" -DCMAKE_POLICY_DEFAULT_CMP0025=NEW -DCMAKE_POLICY_DEFAULT_CMP0060=NEW -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_MAKE_PROGRAM=/usr/bin/make -DCMAKE_MODULE_PATH="/opt/local/share/cmake/Modules" -DCMAKE_PREFIX_PATH="/opt/local/share/cmake/Modules" -DCMAKE_BUILD_WITH_INSTALL_RPATH:BOOL=ON -DCMAKE_INSTALL_RPATH="/opt/local/lib" -Wno-dev -DPython_ADDITIONAL_VERSIONS=3.9 -DICONV_INCLUDE_DIR=/opt/local/include -DICONV_LIBRARY=/opt/local/lib/libiconv.dylib -DCMAKE_OSX_ARCHITECTURES="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET="12.0" -DCMAKE_OSX_SYSROOT="/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.9.2
:info:configure Exit code: 134
:error:configure Failed to configure doxygen: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/main.log for details.

Could it be that the configure script has changed?

[forrie (Forrest)]

As this is an upgrade, I am going to follow the procedures on

​https://trac.macports.org/wiki/Migration

as perhaps that is what I should have done (please note if so). Thanks.

[reneeotten (Renee Otten)]

Yes, that's indeed what you need to do. If the issue persists you can reopen this ticket and then please make sure to attach the main.log file mentioned in the error message.