Paul,

Thank you very much for your followup.

Here is what I get:

$ which tclsh
/sw/bin/tclsh
[15:57:[EMAIL PROTECTED]:~]
$ tclsh
% array get tcl_platform
osVersion 8.8.1 byteOrder littleEndian machine i386 platform unix os Darwin user suzume wordSize 4
% [15:58:[EMAIL PROTECTED]:~]
$ /usr/bin/tc
tclsh       tclsh8.4    tclsh8.4.7  tclsh8.5    tcopy
[15:58:[EMAIL PROTECTED]:~]
$ /usr/bin/tclsh
% array get tcl_platform
osVersion 8.8.1 byteOrder bigEndian threaded 1 machine {Power Macintosh} platform unix os Darwin user suzume wordSize 4

So, the tclsh from fink is what seems to be interacting with the whole process...

I just purged tcltk and all the related packages from fink and the "./ configure", "make", "sudo make install" worked flawlessly:

Congratulations, you have successfully installed the DarwinPorts system.

To get the Portfiles and update the system run:

sudo port selfupdate

Please read README_RELEASE1 and port(1).


Now, I tried "sudo port selfupdate" but I get same Pextlib message :(

JC


On 14 déc. 06, at 15:42, Paul Guyot wrote:

Le 14 déc. 06 à 15:30, Jean-Christophe Helary a écrit :

I've installed XCode 2.4.1, reboot, re-downloaded MacPorts 1.3.1 for OSX 10.4, installed seemingly successfully but a "sudo port selfupdate" still produces the same error.

Besides, I've tried the "./configure" command for the tar package and I still get a "tcl has been compiled with the nothread option" error message that aborts the configuration.

So I am left with no way whatsoever to run macports...

Could you please do:
* which tclsh
* tclsh
 then
 $ array get tcl_platform
* /usr/bin/tclsh
 then
 $ array get tcl_platform

and report the result here.

Thanks.

I'm guessing that configure is picking another tclsh that doesn't have threaded support built-in. On a 10.4.8 MacMini with all software updates and Xcode but nothing else, the built-in tclsh has threaded support built-in.

Besides, I think your default tclsh cannot load Pextlib, either because it doesn't like Pextlib (seems to be the problem that was solved by upgrading Xcode on Intel machines) or because it doesn't load libraries the way MacOS X's default tcl loads them.

Paul
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to