[Starkit] System Library mismatches

[Tom Poindexter]

On Mon, Nov 28, 2005 at 10:07:47AM +0100, Jean-Claude Wippler wrote:

> >  In other work I've been running into problems with stdlibc++
> >and such being either version 2.3.4 or 3.0 on different systems,
> >and software that relies on the libraries getting hosed.  It seems
> >like some distros are not using the naming conventions the way
> >I thought they were designed to be used.
> 
> ... which explains why I'm moving towards a total replacement of  
> Mk4tcl.  C++ deployment is a joke.
> 
> >  Is there a way to force a starpack to a fully static build, rather
> >than relying on system shared libraries?
> 

Clif & JC,

I posted a patch to genkit back in September that allowed me
to statically link libstdc++ when building TclKit.  See my messages:

http://www.equi4.com/pipermail/starkit/2005-September/002514.html
http://www.equi4.com/pipermail/starkit/2005-September/002521.html

My patch requires a 'genkit.local' file to enable static linking.  The
first post has the contents of my genkit.local that enables the static link.
This did not statically link libc, but you could probably follow the
same example to build with '-static' also.

Good luck.

-- 
Tom Poindexter
tpoindex at nyx.net
http://www.nyx.net/~tpoindex/