Still 'Failed to build p5.28-wx: command execution failed' after following the #61588

[specbin]

Since the last question has been closed and I do not have any coding experience with Perl or C++ and am just trying to use the Macports to install the Demeter for XAS analysis, here I am again.

I (think) followed the comment 4 instruction from #61588 -> download the .diff file -> drag it into '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/perl/p5-wx/files' -> use console add the line 'patchfiles patch-C-Compiler-Used-For-C++.diff' in the Portfile (the one in the folder 'p5-wx')

Is this the right way to fix the p5.28-wx bug on macOS Monterey (v12.4)? Thank you so much.

================= here is the console reply, the main.log was also attached.

(base) mac$ sudo port install p5.28-wx
Password:
Portfile changed since last build; discarding previous state.
--->  Computing dependencies for p5.28-wx
--->  Fetching archive for p5.28-wx
--->  Attempting to fetch p5.28-wx-0.993.200_0.darwin_21.arm64.tbz2 from https://packages.macports.org/p5.28-wx
--->  Attempting to fetch p5.28-wx-0.993.200_0.darwin_21.arm64.tbz2 from https://cph.dk.packages.macports.org/p5.28-wx
--->  Attempting to fetch p5.28-wx-0.993.200_0.darwin_21.arm64.tbz2 from https://kmq.jp.packages.macports.org/p5.28-wx
--->  Fetching distfiles for p5.28-wx
--->  Verifying checksums for p5.28-wx
--->  Extracting p5.28-wx
--->  Applying patches to p5.28-wx
--->  Configuring p5.28-wx
--->  Building p5.28-wx                                  
Error: Failed to build p5.28-wx: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-wx/p5.28-wx/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.
Error: Processing of port p5.28-wx failed

[jmroot (Joshua Root)]

Please add any further discussion of this issue to the older ticket. We want to have only one ticket for each issue so that all the information about it is in one place.

If the patch attached to #61588 was considered an acceptable solution, presumably the port's maintainer would have committed it already and closed the ticket. So I would guess a better way to make the build use the appropriate compiler still needs to be found.