[Top] [All Lists]

Re: [TDK] TDK 4.1 tclapp and shared libraries

Subject: Re: [TDK] TDK 4.1 tclapp and shared libraries
From: "Virden, Larry W."
Date: Tue, 10 Jun 2008 07:23:50 -0400
Jeff, I've read and that makes it
seem pretty simple to build a library with stubs. I've also read over , (which seems rather
negative in tone at the beginning),  and a few other places on the wiki.

As I said, the howto seems to make it sound pretty simple. For a simple
extension, are there any gotchas?  

<URL: >
Even if explicitly stated to the contrary, nothing in this posting
should be construed as representing my employer's opinions.
<URL: mailto:lvirden@xxxxxxxxx > <URL:

-----Original Message-----
From: Jeff Hobbs [mailto:jeffh@xxxxxxxxxxxxxxx] 
Sent: Monday, June 09, 2008 3:46 PM
To: Virden, Larry W.
Cc: tdk@xxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [TDK] TDK 4.1 tclapp and shared libraries

Virden, Larry W. wrote:
> So, the developer trying to use TDK 4.1 that I've been discussing, 
> through some force feeding of information, finally got his application

> to wrap. This app consists of some tcl scripts and 2 personal shared 
> libraries.
> When he runs this wrapped application, he gets:
> couldn't load file "/tmp/tclTXG09B": /tmp/tclTXG09B: undefined symbol:
> Tcl_Alloc

My bet is that this extension was not properly built with stubs support.

  That is required for single-file executables, where there will be no on the system.  That is one of the design values of stubs.

TDK mailing list

<Prev in Thread] Current Thread [Next in Thread>