On Apr 7, 2008, at 2:53 PM, Ryan Schmidt wrote:
On Apr 6, 2008, at 22:31, Kok-Yong Tan wrote:
In the midsts of a "sudo port -vR upgrade installed" command on a
dual 2GHz PowerMac G5 OS 10.4.11 system, it reported this error:
Error: Target org.macports.checksum returned: Could not open file: /
opt/local/var/macports/distfiles/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/libxslt/
libxslt/libxslt/libxslt/libxslt/libxslt-1.1.22.tar.gzWarning: the
following items did not execute (for libxslt):
org.macports.activate org.macports.extract org.macports.checksum
org.macports.patch org.macports.configure org.macports.build
org.macports.destroot org.macports.installError: The following
dependencies failed to build: gtk-doc scrollkeeper libxslt p5-xml-
parserError: Unable to upgrade port: 1
I looked at /opt/local/var/macports/distfiles/libxslt/ and
libxslt-1.1.22.tar.gz is certainly there. Why is there the
extraneous additions of libxslt in the above absolute file path and
how can I fix it (where's the makefile or whatever it uses)?
I have seen this problem myself, but never could determine what
caused it. I don't use the -R option. Maybe you should not use it
either.
The problem is not the libxslt Makefile, or any other Makefile;
there must be a problem in MacPorts base. If anyone can find a
consistent way to reproduce this duplicated distfile directory
issue, please file a bug.
I think the problem is connected with multiple listings of dependency
on port being installed.
You are installing or upgrading Port A. The register lists the ports
that depend on A thus:
Port B
Port C
Port D
Port C
Port C
Port B
Port E
Port B
Port C
etc etc
This list appears to lengthen every time you do sudo port -dfun
upgrade PortA. Since the same things happen with other Ports, the
process of doing a sudo port -dfunR upgrade PortA and upgrading all
its dependents gets very complex and time consuming with the same
port(s) being re-installed many many times. Perhaps circular
dependents get created. In any event, we need (pending a real fix
that eliminates multiple entires for the same dependent) a tool to
purge duplicates from the Registry entries for depends of the same port.
I did write this up at some point and file a ticket. Never heard
anything back.
Just to be clear: Im talking about the Ports that depend on Port A and
NOT the Ports that Port A depends upon to install.
William Davis
frstanATbellsouthDOTnet
Mac OS X.5.2 Darwin 9.2.2
Xquartz 2.2.0 - (xorg-server 1.3.0-apple13)
Mac Mini Intel Duo @ 1.86 GHz
Mundus vult decepi, ego non
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
