[Starkit] Re: trying to compile tclkit: 64-bit SPARC 8.5a4

[Tim Edwards]

An update -- I managed to get a working 64-bit tclkitlite, so I can now load
my 64-bit .so files just fine.  I now have to use the 32-bit tclkit to build
my "binary", embedding the 64-bit tclkitlite for runtime.

I would STILL rather just have a 64-bit tclkit to simplify my methodology
(or a tclkitlite with all the kit-building powers of tclkit), but I guess
I'm the only one needing 64-bit on this platform.

On 5/26/06, Tim Edwards <tim.j.edwards at gmail.com> wrote:
>
> I've managed to get most of the way through building a 64bit version of
> 8.5a4 by using "-mcpu-v9 -m64" during compilation in all the appropriate
> places.  After finally convincing all of the components to build 64-bit
> libraries (fairly minor tweaking and some library re-ordering at link), I
> finally get all the way to genkit phase 'D' and get this failure:
>
>   $ tclsh genkit D
>   copying install/sc0043/kitsh to dummy85-sc0043
>   application-specific initialization failed: couldn't read file
> "/tmp/tclkit8.5a4/dummy85-sc0043/lib/tcl8.5/init.tcl": not a directory
>      info loaded = {{} zlib} {{} vfs} {{} rechan} {{} Mk4tcl}
>    tclkit_version = 1
>  invalid command name "parray"
>
> If I run the "dummy" directly, it does this:
>
>  $ ./dummy85-sc0043
>  application-specific initialization failed: unknown encoding "iso8859-1"
>
> On a different platform (i686 red hat linux), the dummy doesn't give this
> failure, it just gives a prompt.  Since "init.tcl" is, indeed in the "
> runtime85.kit" file which gets appended to the dummy executable, this
> seems to be a problem with the virtual filesystem.  It's strange to me that
> the 'genkit' invocation seems to be able to access the encoding from the vfs
> (but then fails to find init.tcl), while the direct dummy invocation can't
> even find the encodings.
> Does anyone know what I might be able to try to get past this? I
> appreciate any suggestions!
> Regards,
> _Tim
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.equi4.com/pipermail/starkit/attachments/20060605/b0eb1a57/attachment.htm