building gtk-engines2 fails on Tiger - PPC

[drechsel@…]

Error message:

Command output: sh: line 1: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_gtk-engines2/work/gtk-engines-2.18.4

Workaround:

cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_gtk-engines2/work/

mv gtk-engines-2.18.2 gtk-engines-2.18.4

[drechsel@…]

Sorry - my error message was incomplete:

--->  Building gtk-engines2
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_gtk-engines2/work/gtk-engines-2.18.4" && /usr/bin/make -j1 all " returned error 1
Command output: sh: line 1: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_gtk-engines2/work/gtk-engines-2.18.4: No such file or directory

[ryandesign (Ryan Carsten Schmidt)]

I don't see how this bug can possibly be valid. On my Snow Leopard machine, gtk-engines2 @2.18.4 definitely extracts a directory called gtk-engines-2.18.4 as it should. I can't see how it could possibly extract a directory called gtk-engines-2.18.2 on Tiger. You must have had an old gtk-engines-2.18.2 directory lying around from a previous build attempt when the port was at that version, that was for some inexplicable reason not detected as being older than the 2.18.4 portfile, and therefore not automatically cleaned up when you tried again with 2.18.4.

For good measure, I updated gtk-engines2 to 2.18.5.