xmlto @0.0.29: /opt/local/bin/bash: Segmentation fault: 11

[RobArthan]

Essentially what is says in the summary: I can't xmlto on Apple Silicon MacBook Pro running Sequoia 15.3.2.

I have tried updating my ports and cleaning xmlto. From the logs it looks like the step that fails is a call of make in the directory /opt/local/var/macports/build/xmlto-2017445c/work/xmlto-0.0.29. When I navigate to that directory and run the make command this is what I see

rda]- make -j14 -w all
make: Entering directory `/opt/local/var/macports/build/xmlto-2017445c/work/xmlto-0.0.29'
/Applications/Xcode.app/Contents/Developer/usr/bin/make  all-am
make[1]: Entering directory `/opt/local/var/macports/build/xmlto-2017445c/work/xmlto-0.0.29'
FORMAT_DIR=./format /opt/local/bin/bash ./xmlto --skip-validation -o man/man1 man doc/xmlto.xml
FORMAT_DIR=./format /opt/local/bin/bash ./xmlto --skip-validation -o man/man1 man doc/xmlif.xml
make[1]: *** [man/man1/xmlto.1] Segmentation fault: 11
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [man/man1/xmlif.1] Segmentation fault: 11
make[1]: Leaving directory `/opt/local/var/macports/build/xmlto-2017445c/work/xmlto-0.0.29'
make: *** [all] Error 2
make: Leaving directory `/opt/local/var/macports/build/xmlto-2017445c/work/xmlto-0.0.29'

[ryandesign (Ryan Carsten Schmidt)]

Please attach the main.log file so that we can see what the problem was.

From the output you posted, it appears that xmlto is using MacPorts bash, and MacPorts bash is crashing for some reason. If you attach the crash log, that might explain why it's crashing. However, manually running make outside of MacPorts is not equivalent to what MacPorts does and is not necessarily a valid indicator of what went wrong when MacPorts did the build.

The problem that xmlto is using MacPorts bash at all (it's not declared as a dependency) is #71720. You could therefore theoretically work around the problem by running:

sudo port -f deactivate bash
sudo port clean xmlto
sudo port install xmlto
sudo port activate bash

[RobArthan]

main.log file

[RobArthan]

The suggest work-around works. Thanks for that.