Re: Starkit causes suddenly ELF Header issue

Am 02.12.2010 14:27, schrieb Pat Thoyts:
> Are you using 64bit linux? Make sure your package library is suitable
> for the tcl executable you are using. You cannot load 64bit libraries
> into 32 bit processes.

Yes there are 64bit libraries for the sha256 module present and I am 
running a 32bit Linux:

$ tree -L 2 -F
.
|-- Darwin-x86/
|   |-- critcl.tcl*
|   `-- sha256c.dylib*
|-- Linux-x86/
|   |-- critcl.tcl
|   `-- sha256c.so*
|-- Linux-x86_64/
|   |-- critcl.tcl
|   `-- sha256c.so*
|-- Windows-x86/
|   |-- critcl.tcl
|   `-- sha256c.dll*
|-- critcl.tcl
`-- pkgIndex.tcl

[twofish]$ tree -L 1
.
|-- LICENSE.txt
|-- f32-Linux-x86.so
|-- f32-Linux-x86_64.so
|-- f32-critcl.tcl
|-- pkgIndex.tcl
|-- twofish.tcl
`-- twotest.tcl

I removed f32-Linux-x86_64.so and the folder Linux-x86_64 but I am 
getting still the load error

> Or possibly you simply generated something that is not a shared object
> (aka dll).
> Also, to load an extension into a tclkit, the extension package must
> have been compiled using Tcl stubs.

Hm, Critcl made all the compiling stuff. I think it uses stubs per 
default, doesn't it?

> The tmp filename is because shared libraries are loaded by the
> system's ld.so which doesn't understand tcl virtual filesystems. So we
> copy the shared library out into the tmp directory and have that
> loaded up.
>

Thank you for the hint. So probably on the Mac I had no problem because 
Snow Leopard is per default running 64bit coded.

Although sha256c (tcllib) compiled well into a starkit. It is the 
twofish extension which is newly added, so I will have a glance on it.







-- 
You received this message because you are subscribed to the "starkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/starkit?hl=en