can't read "configure.ld_archflags" error while upgrading mercurial

Kastus Shchuka macports at tprfct.net
Sun May 16 16:48:57 PDT 2010


Hi,

I noticed a new version of mercurial after running port sync but when  
I tried to upgrade mercurial I bumped into the following error:

--->  Computing dependencies for mercurial
DEBUG: Searching for dependency: python26
DEBUG: Found Dependency: receipt exists for python26
DEBUG: Executing org.macports.main (mercurial)
--->  Fetching mercurial
DEBUG: Executing org.macports.fetch (mercurial)
--->  Verifying checksum(s) for mercurial
DEBUG: Executing org.macports.checksum (mercurial)
--->  Checksumming mercurial-1.5.2.tar.gz
DEBUG: Correct (md5) checksum for mercurial-1.5.2.tar.gz
DEBUG: Correct (sha1) checksum for mercurial-1.5.2.tar.gz
DEBUG: Correct (rmd160) checksum for mercurial-1.5.2.tar.gz
--->  Extracting mercurial
DEBUG: Executing org.macports.extract (mercurial)
--->  Extracting mercurial-1.5.2.tar.gz
DEBUG: setting option extract.args to /opt/local/var/macports/ 
distfiles/python/mercurial-1.5.2.tar.gz
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_devel_mercurial/work" && /usr/bin/gzip - 
dc /opt/local/var/macports/distfiles/python/mercurial-1.5.2.tar.gz | / 
usr/bin/gnutar --no-same-owner -xf -'
DEBUG: Executing org.macports.patch (mercurial)
--->  Configuring mercurial
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (mercurial)
--->  Building mercurial
DEBUG: Executing proc-pre-org.macports.build-build-0
Error: Target org.macports.build returned: can't read  
"configure.ld_archflags": no such variable
DEBUG: Backtrace: can't read "configure.ld_archflags": no such variable
     while executing
"$pre $targetname"
Warning: the following items did not execute (for mercurial):  
org.macports.destroot org.macports.build
DEBUG:
Error: Unable to upgrade port: 1

I tried to search in trac and saw similar errors reported (and fixed)  
in other ports. I am not sure that I discovered something new as there  
is an upgrade to v 1.5.3 commited yesterday.

Shall I file a trac ticket for this one?

It's on PPC iBook G4 running OSX 10.5.8, macports 1.8.2.

Thanks,

-Kastus


More information about the macports-users mailing list