Max Asato wrote: > On Wed, Dec 10, 2008 at 08:59:55AM +0100, Anders F Bj?rklund wrote: >> If you run MacPorts in debugging mode (port -d), you should get >> some output telling you what happened to the unarchive phase... >> But when you enable portarchivemode=yes, it is supposed to try >> "unarchive" (binary) before doing the "destroot" (source build) >> >> --anders > > I tried forcing a binary install with the -b option at Josh's suggestion > but that still didn't work. Here's a test for a glib2 archive that > I copied over from another Mac/Intel system. > > imac2$ ls -l /opt/local/var/macports/packages/darwin/i386/glib2* > -rw-r--r-- 1 root admin 3629276 Dec 8 13:18 > /opt/local/var/macports/packages/darwin/i386/glib2-2.18.3_0+darwin_8.i386.tgz > > imac2$ sudo port -b install glib2 > Error: Target org.macports.unarchive returned: Archive for glib2 2.18.3_0 not > found, required when binary-only is set! > Error: Status 1 encountered during processing. > > Is there any other package metadata that gets referenced before MacPorts > looks at the archive directory? I'll try the -d option to get more > diagnostic info tonight.
Do you have the same portarchivetype set on both systems? - Josh _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
