smlnj @110.72 build failure when 110.71 is installed

[avysk (Alexey Vyskubov)]

PowerMac 2 x G5, Mac OS X 10.5.8

smlnj 110.71 is installed.

Upgrade to 110.72 fails:

[parsing $/(ckit-lib.cm):ast/(group.cm):extensions/c/pp-ast-ext-fn.sml]
FAILURE: stabilization failed
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_smlnj/work/smlnj-110.72/config/install.sh: !!! Installation of libraries and programs failed.
shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_smlnj/work/smlnj-110.72" && /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_smlnj/work/smlnj-110.72/config/install.sh " returned error 1
Warning: the following items did not execute (for smlnj): org.macports.destroot org.macports.build
Log for smlnj is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_smlnj/main.log
To report a bug, see <http://guide.macports.org/#project.tickets>

Full log is attached.

[avysk (Alexey Vyskubov)]

Build log

[markemer (Mark Anderson)]

Workaround: Uninstalling 110.71 and installing 110.72 works. Not sure why it fails when upgrading.

[jabial@…]

Replying to emer@…:

Workaround: Uninstalling 110.71 and installing 110.72 works. Not sure why it fails when upgrading.

This worked for me too. This indicates that the 110.71 smlnj is not able to compile the 110.72 version. It should be solved by forcing the use of the bootstrap one which is downloaded.

[wiml@…]

This workaround worked for me too, 10.6.5 on a Core2Duo.

[Robert.Betz@…]

I cannot get this to compile either. Using Intel Mac, Snow Leopard 10.6.7. Tried uninstalling and reinstalling but still get the same error. Stopping me from installing other ports that are dependent on it.

[ryandesign (Ryan Carsten Schmidt)]

The conflicts_build portgroup can be used to at least give users an error message that explains the problem and gives them a solution.

Near the top of the portfile, put:

PortGroup conflicts_build 1.0

Then later, near the configure and build options, put:

conflicts_build-append ${name}

[mf2k (Frank Schima)]

See #54043

[tobypeterson]

I haven't seen this problem when upgrading more recent versions. So... worksforme?