Information needed to fix build problem

[Ryan Schmidt]

On Jul 19, 2007, at 09:13, Marv Abe wrote:

> I have a problem re-building only the clamav package after aborting  
> the
> package fetching and manually attempting to cleanup after my  
> snafu.  Seems
> that I really messed up by only doing a partial cleanup.
>
> I have MacPorts 1.5.  If anyone can point me to some hints or  
> documents on
> what to look for in my build system to right myself, it would be
> appreciated.  Here's where I am at:
>
>
> ddb029:/opt/local/var/db/dports/build # port -d install  clamav
> DEBUG: Found port in
> file:///opt/local/var/macports/sources/rsync.macports.org/release/ 
> ports/sysu
> tils/clamav
> DEBUG: Changing to port directory:
> /opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> sysutils/cl
> amav
> DEBUG: couldn't change working directory to
> "/opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> sysutils/c
> lamav": no such file or directory
>     while executing
> "cd $portpath"
>     (procedure "mportopen" line 28)
>     invoked from within
> "mportopen $porturl [array get options] [array get variations]"
> Error: Unable to open port: couldn't change working directory to
> "/opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> sysutils/c
> lamav": no such file or directory

Try

sudo port clean --all clamav

Then try installing clamav again.

If you still get the same error... Since it says the directory "/opt/ 
local/var/macports/sources/rsync.macports.org/release/ports/sysutils/ 
clamav" does not exist, how much of that path does exist?

On my system I only have up to /opt/local/var/macports; I don't have  
a "sources" directory in there. But I've configured my MacPorts to  
use a Subversion working copy located elsewhere, instead of the  
default rsync configuration, so that may be the reason for that on my  
system. On yours, I'm not sure yet.