qtscriptgenerator failed to build

[sandman1687@…]

Installing Amarok using 1.8.2 on Snow Leopard gets to qtscriptgenerator, then fails. Terminal output:

 sudo port install amarok -d
Password:
--->  Computing dependencies for amarok
--->  Building qtscriptgenerator
Error: Target org.macports.build returned: shell command "cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_qtscriptgenerator/work/qtscriptgenerator-src-0.1.0/generator && export QTDIR=/opt/local/libexec/qt4-mac && PATH=/opt/local/libexec/qt4-mac/bin:/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin qmake && make && /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_qtscriptgenerator/work/qtscriptgenerator-src-0.1.0/generator/generator" returned error 138
Command output: make -f Makefile.Release
make[1]: Nothing to be done for `first'.
sh: line 1:   309 Bus error               /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_qtscriptgenerator/work/qtscriptgenerator-src-0.1.0/generator/generator

Error: The following dependencies failed to build: qtscriptgenerator taglib taglib-extras
Error: Status 1 encountered during processing.
Before reporting a bug, first run the command again with the -d flag to get complete output.

[jmroot (Joshua Root)]

Please remember to preview and use WikiFormatting, and fill in the Port field.

[ryandesign (Ryan Carsten Schmidt)]

qtscriptgenerator installed ok for me today on Snow Leopard. Maybe clean and try again? Use the debug switch so that if it fails again, you can attach the complete output here, which might give us further clues.

[mbrehmer@…]

I observed the same error (error 138) while building qtscriptgenerator. May I attach my debug output?

[michaelld (Michael Dickens)]

Cc Me!

[michaelld (Michael Dickens)]

As of r69497, Amarok is at version 2.3.1; please see ticket #25489 for more info. I don't think this ticket is relevant any longer, so I'm closing it; please verify and reopen if the original topic is still an issue.