Soundtouch uses system aclocal files which makes it fail to autoreconf on 10.5

[ygramul.el.multiple@…]

When upgrading from soundtouch 1.5.0_0 to 1.5.0_1, soundtouch fails during the configure stage:

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I config/m4
aclocal: aclocal: file `config/m4/lt~obsolete.m4' does not exist
autoreconf: aclocal failed with exit status: 1

See attached logs for more details. I'm running MacPorts 1.9.2 under Mac OS X 10.5.8, and Xcode is version 3.1.2

[ygramul.el.multiple@…]

Log file for soundtouch

[jmroot (Joshua Root)]

Works on 10.6, which suggests it's using the system aclocal dir for some reason.

[dbevans (David B. Evans)]

Confirming that it fails in similar fashion on both 10.4 and 10.5.

[dbevans (David B. Evans)]

Cc Me!

[elelay (Eric Le Lay)]

I'd say this is because config/m4/lt~obsolete.m4 is a symlink to /usr/share/aclocal/lt~obsolete.m4

see :

$ ll config/m4/
total 40
lrwxrwxrwx   1 root  admin  29 19 déc 18:15 libtool.m4 -> /usr/share/aclocal/libtool.m4
lrwxrwxrwx   1 root  admin  31 19 déc 18:15 ltoptions.m4 -> /usr/share/aclocal/ltoptions.m4
lrwxrwxrwx   1 root  admin  29 19 déc 18:15 ltsugar.m4 -> /usr/share/aclocal/ltsugar.m4
lrwxrwxrwx   1 root  admin  31 19 déc 18:15 ltversion.m4 -> /usr/share/aclocal/ltversion.m4
lrwxrwxrwx   1 root  admin  33 19 déc 18:15 lt~obsolete.m4 -> /usr/share/aclocal/lt~obsolete.m4

Deleting everything inside soundtouch/config/m4 seems to fix the issue (the .m4 files get regenerated from /opt/local/share/aclocal). soundtouch then builds correctly.

[elelay (Eric Le Lay)]

fixed in r74502 I used exec rm because the delete macro failed. If somebody knows a better way ?...

[jmroot (Joshua Root)]

Unfortunately delete doesn't accept multiple file args. file delete does, and will work fine in this case since you're not deleting any non-empty directories.

[elelay (Eric Le Lay)]

Replying to jmr@…:

Unfortunately delete doesn't accept multiple file args. file delete does, and will work fine in this case since you're not deleting any non-empty directories.

Thanks for the answer. the guide is misleading then :

 delete file ...

    Deletes each of the given files/directories. Behaves similarly to file delete -force except that file delete -force will fail to delete directories properly on 10.3 systems. 

file delete [glob ${worksrcpath}/config/m4/*.m4] didn't work either. Only eval file delete [glob ${worksrcpath}/config/m4/*.m4] did the trick. I updated the portfile to use file delete in r74523.