On 10/30/07, markd@macports.org <markd@macports.org> wrote:

"Soo-Hyun Choi" <s.choi@hackers.org.uk> writes:
>If I attache more detailed error message, it would something like:
>
>
>soohyunc@davinci: ~ $ sudo port install xorg-proto
>--->  Fetching xorg-proto
>--->  Verifying checksum(s) for xorg-proto
>--->  Extracting xorg-proto
>--->  Configuring xorg-proto
>--->  Building xorg-proto with target all
>--->  Staging xorg-proto into destroot
>--->  Packaging tgz archive for xorg-proto 20070907_0
>Error: Target org.macports.archive returned: error copying
>"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/.macports.xorg-
>proto.state" to
>"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/destroot/+STATE":
>no such file or directory
>Error: Status 1 encountered during processing.
>soohyunc@davinci: ~ $

That port is supposed to do nothing but trigger dependencies.

fetch           { }
checksum        { }
configure       { }
build           { }
destroot        { }
activate        { }

Is there another stage that needs to be eliminated?  I'm not familiar with
ports like this.

Mark