1.8 selfupdate to 1.8.1 fails resulting in Tcl problems

[ben-macports@…]

After reinstalling Macports 1.8.0 after migrating from Leopard to Snow Leopard. I upgraded OS X from 10.6 --> 10.6.1. On 28 September 2009, I ran "sudo port selfupdate" to upgrade from 1.8.0 to the new 1.8.1 which resulted in the following error when running port:

~ benc$ port
dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable image found.  Did find:
	/Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong architecture
    while executing
"load /Library/Tcl/macports1.0/MacPorts.dylib"
    ("package ifneeded macports 1.0" script)
    invoked from within
"package require macports"
    (file "/opt/local/bin/port" line 39)

[blb@…]

What is the result of the following?

$ lipo -info /Library/Tcl/macports1.0/MacPorts.dylib

[jmr@…]

Also

ls -l `which gcc`

[ben-macports@…]

$ lipo -info /Library/Tcl/macports1.0/MacPorts.dylib
Non-fat file: /Library/Tcl/macports1.0/MacPorts.dylib is architecture: i386

$ ls -l `which gcc`
lrwxr-xr-x  1 root  wheel  7 Sep 15 17:12 /usr/bin/gcc -> gcc-4.2

$ gcc --version
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5646)
Copyright (C) 2007 Free Software Foundation, Inc.

[pali@…]

Cc Me!

[oscartheduck@…]

Writing to confirm this bug. I just upgraded to Snow Leopard and then 10.6.2, same error:

metatron:~ james$ sudo port update
Password:
dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable image found.  Did find:
	/Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong architecture
    while executing
"load /Library/Tcl/macports1.0/MacPorts.dylib"
    ("package ifneeded macports 1.0" script)
    invoked from within
"package require macports"
    (file "/opt/local/bin/port" line 39)

[tclemons@…]

Cc Me!

[pali@…]

Ehm... As described in Richard Dooling's ​MacPorts On Snow Leopard, the fix is to install new MacPorts 1.8.1 for Snow Leopard over the old one and follow the migration instructions.

I think this renders this bug 'invalid', right?

[ryandesign@…]

Replying to pali@…:

the fix is to install new MacPorts 1.8.1 for Snow Leopard over the old one and follow the migration instructions.

It sounds like that's the problem, yes. But the original reporter said he "reinstall[ed] Macports 1.8.0 after migrating from Leopard to Snow Leopard". He could certainly try following the instructions again, though; maybe a step was missed the first time.

[jmr@…]

As far as I'm aware no developer has been able to reproduce this. Either you didn't do the migration right or your gcc is producing i386 binaries on an x86_64 system, which would be an Apple bug.