w3m-devel build failure on macOS Big Sur 11.0.1 beta using xcode 12.2 beta

[chicagotripp (Altoine Barker)]

I'm receiving the following build failure:

ranlib libwc.a
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_w3m/w3m-devel/work/tats-w3m-b65f7b2/libwc'
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_w3m/w3m-devel/work/tats-w3m-b65f7b2'
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_w3m/w3m-devel/work/w3m-b65f7b243dc156f0b6b7dfa0dae4152942e33bea" && /usr/bin/make -j16 -w all 
Exit code: 2
Error: Failed to build w3m-devel: command execution failed
DEBUG: Error code: CHILDSTATUS 19574 2
DEBUG: Backtrace: command execution failed
    while executing
"system {*}$notty {*}$callback {*}$nice $fullcmdstring"
    invoked from within
"command_exec -callback portprogress::target_progress_callback build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_www_w3m/w3m-devel/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port w3m-devel failed

[chicagotripp (Altoine Barker)]

w3m-devel main.log file

[chicagotripp (Altoine Barker)]

I'm came across this error running this command:

sudo port -d install gimp +animation

I said "Yes to install recommended ports but it would consistently fail. So, I than run:

sudo port clean w3m && sudo port install w3m-devel

and then I receive the error message as I had first posted. I choose this port as it is actively worked on despite the original w3m port having not been worked on since 2011.

[ryandesign (Ryan Carsten Schmidt)]

Ok, so it's unfortunately the same error as seen in w3m. You should report the problems to the developers of w3m-devel: ​https://github.com/tats/w3m

Duplicate of #61356.