php5-curl 5.3.8 fails to install under Leopard (PPC)

[alun.j.carr@…]

When I do a sudo port -v upgrade outdated, I get the following (MacPorts 2.0.3, Xcode 3.1.4, OS X 10.5.8, 12" PowerBook G4):

--->  Verifying checksum(s) for php5-curl
--->  Checksumming php-5.3.8.tar.bz2
--->  Extracting php5-curl
--->  Extracting php-5.3.8.tar.bz2
--->  Configuring php5-curl
Configuring for:
PHP Api Version:         20090626
Zend Module Api No:      20090626
Zend Extension Api No:   220090626
shtool:path:Error: failed to create temporary directory `/tmp/.shtool.21867'
touch: /tmp/.shtool.21867/shtool.tmp: No such file or directory
shtool:path:Error: failed to create temporary directory `/tmp/.shtool.21937'
touch: /tmp/.shtool.21937/shtool.tmp: No such file or directory
autom4te: cannot create /tmp/am4t413.22007: Permission denied
 at /opt/local/bin/autom4te line 957
shell command "cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_php_php5-curl/php5-curl/work/php-5.3.8/ext/curl && /opt/local/bin/phpize" returned error 1
Error: Target org.macports.configure returned: shell command failed (see log for details)
Warning: the following items did not execute (for php5-curl): org.macports.install org.macports.configure org.macports.build org.macports.destroot
Log for php5-curl is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_php_php5-curl/php5-curl/main.log
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>

[alun.j.carr@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Please remember to use WikiFormatting. You don't need to Cc yourself when you are the reporter but please do Cc the maintainer of the port.

It seems there is something wrong with your /tmp directory, in that it has restricted permissions. The /tmp directory should have very open permissions such that any user or process can create things there. What is the output on your system of the command:

ls -ld /tmp /private/tmp

[alun.j.carr@…]

Problem fixed after selfupdate the upgrade outdated today.