[Starkit] Mandrake 7.2 tclkits

[Tom Poindexter]

On Tue, Apr 25, 2006 at 12:07:06AM +0200, Jean-Claude Wippler wrote:
> Guaca Mole wrote:
> 
> >Can you be a bit more specific about what the problems
> >that you found in newer linux distributions with
> >mandrake 7.2-based tclkit builds?
> >
> >It has worked for me fine in a lot of Linux
> >distributions, compiling stdc++ statically
> 
> Well, the main problem right now is not the choice of MD72, but the  
> fact that my vmware-based image is not usable anymore to build on.  I  
> updated vmware over the years, and as of v5 (or 5.5, I forgot), it  
> insisted on "upgrading" the (virtual) hardware of the setup I had  
> running MD72.  After that, the MD72 system no longer recognizes the  
> ethernet card, which makes it quite inconvenient for me to build on.   
> I normally nfs-mount my kit build area on whatever system I want and  
> build using a single setup.


Perhaps QEMU to the rescue?  http://qemu.org/
It won't save your VMWare images, but you probably can bootstrap another
MD7.2 system.  Definitely use the KQEMU Accelerator.



JC, what is your recipe for building the static Linux tclkits?  Is there 
a genkit.local file you use?   Please post.

I might try a tclkit build using the method to statically link libstdc++ 
that I posted last fall on the list.


> Rhetorical question: could there be some Linux distro out there which  
> is specifically designed to produce binaries which can be used on a  
> maximum number of platforms?  If not, why not?  Does no one else on  
> this planet deploy non-trivial binaries for Linux?

Amen.  I happened to speak to a GCC developer a while back about this
situation, especially the problem of statically linking libstdc++.  He
seemed to indicate that the developers of libc and libstdc++ are of a
mindset "why would you ever want to statically link?", and are not
persuaded to provide such capability by our pleas.



-- 
Tom Poindexter
tpoindex at nyx.net