py26-wxpython trouble (even without pgAdmin3)

[Ryan Schmidt]

On Jun 14, 2010, at 21:55, Jim Busser wrote:
> On 2010-06-14, at 3:45 PM, Ryan Schmidt wrote:
>> On Jun 14, 2010, at 14:59, Jim Busser wrote:
>>> 	sudo port -d install py26-psycopg2 +postgresql84
>>> which gave several architecture warnings, among the first of which was
>>> 	ld: warning: in Parser/acceler.o, file was built for unsupported file format which is not the architecture being linked (i386)
>> 
>> So, you didn't ask for the universal variant. And it's trying to do something with i386.
>> 
>> What kind of Mac is this -- 32-bit or 64-bit? If 64-bit, then under snow leopard the default arch is x86_64 not i386 so I would wonder why it was trying to build anything for i386.
>> 
>> What is the value of the build_arch variable in your macports.conf?
> 
> The answer re kind of Mac is 32 bit (the following command returns EFI32 so evidently 32-bit)
> 
> 	ioreg -l -p IODeviceTree | awk -F'"' '/firmware-abi/{print $4}'

The bitness of your EFI doesn't matter; the bitness of your processor does. Find out with:

sysctl hw.cpu64bit_capable

"1" means 64-bit, "0" means 32-bit.


> Thanks also for catching that I had missed that the new MacPorts would leave untouched the old macports.conf (in which I had uncommented build_arch to try i386)

Ok, that explains that. You were trying to build 32-bit, but apparently some of the software you were building did not support changing build_arch.


> so after reverting to the macports.conf.default which the 1.9.0 installer had provided as a contingency and after again doing
>   sudo port -f uninstall installed
>   sudo port clean --work --archive all

Now that you've restored the default config you'll be building 64-bit, which should work for more ports.


> Error: The file /opt/local/lib/libSDL.dylib does not exist, though it was
> Error: expected to have been provided by one of wxWidgets-python's dependencies. Try
> Error: rebuilding the port that should have provided that file by running
> Error: 
> Error:     sudo port -n upgrade --force <portname>

You've found a bug! I fixed it in r68829. Please "sudo port selfupdate" and try again.