On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
>> Ok ther still seems to be an issue with that configure directory not  
>> being created
>> I took a llok and I have nothing in the tree under work in the path  
>> shown in the error
>> [Bluefish:/opt/local] jason% sudo port -d extract apache2
>> DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
>> --->  Extracting apache2
>> DEBUG: Executing org.macports.extract (apache2)
>> --->  Extracting httpd-2.2.11.tar.bz2
>> DEBUG: setting option extract.args to /opt/local/var/macports/ 
>> distfiles/apache2/httpd-2.2.11.tar.bz2
>> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_www_apache2/work" && /opt/local/bin/bzip2 
>> -dc /opt/local/var/macports/distfiles/apache2/httpd-2.2.11.tar.bz2 | 
>> /usr/bin/gnutar --no-same-owner -xf -'
>> sh: /opt/local/bin/bzip2: Bad CPU type in executable

Was this MacPorts install copied over from a different architecture (eg from
a PowerPC to Intel)?

Odd though that it continued on after that as it should have failed at this
point instead of continuing.


macports-users mailing list

Reply via email to