autoconf @2.69 build failure - missing autoreconf.in

[johanvz602@…]

OS X 10.6.8.

buri:~ # xcodebuild -version
Xcode 3.2.6
Component versions: DevToolsCore-1809.0; DevToolsSupport-1806.0
BuildVersion: 10M2518

When building from source ("buildfromsource always" in macports.conf):

buri:~ # port clean autoconf &&  port install autoconf
--->  Cleaning autoconf
--->  Computing dependencies for autoconf
--->  Fetching distfiles for autoconf
--->  Verifying checksum(s) for autoconf
--->  Extracting autoconf
Error: reinplace: couldn't read file "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_autoconf/autoconf/work/autoconf-2.69/bin/autoreconf.in": no such file or directory
Error: org.macports.patch for port autoconf returned: reinplace sed(1) failed
Please see the log file for port autoconf for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_autoconf/autoconf/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port autoconf failed

(Of course, a workaround is to install the pre-built autoconf package.)

[johanvz602@…]

Cc Me!

[johanvz602@…]

nevermind - my apologies, this was a strange configuration problem on my machine. I think the trouble was that there were an extraction program (xz) on my Mac within a mode 0000 directory (/usr/pkg) that macports found when i built and installed it, and it was trying to use this program to extract the macports source, and failing.

Please close this ticket!

[rogerdpack@…]

for followers, I just got this, and for me it meant that extract was using a "separately installed" /usr/local/bin/xz executable, which for some reason caused the extract ? to fail. Renaming that file caused it to build as normal.