[kaffe] Re: Problem getting a real static kaffe-bin for ARMuClinux

[David Tiller]

Thank you all for your assistance. 

I guess what I mean by a 'real' static executable is one where all of the executable code is in a single file. There are absolutely no dependencies on external libs of any kind; dynamic, semi-static, faked by libtool - nothing. There are no embedded paths, so you can run it from anywhere. 

As long as a semi-static (libtool-faked) executable will work under uClinux on an ARM 9, I'll be happy.

Thanks again!

-----Original Message-----
From:	Kiyo Inaba [mailto:inaba at src.ricoh.co.jp]
Sent:	Fri 1/21/2005 9:02 AM
To:	andrea.scian at wawnet.biz
Cc:	kaffe at kaffe.org; inaba at src.ricoh.co.jp
Subject:	Re: [kaffe] Re: Problem getting a real static kaffe-bin for ARMuClinux
Hi Andrea,

You wrote:
>Due the fact that Kaffe uses libtool you will never get a "real" static
>executable, but you can only have a "semi-static" executable that will NOT
>use the Linux dynamic library loading but will make all this works on its
>own (IOW: kaffe-bin itself loads libnative and extract the right function
>pointer). I'm not an expert of libtool (I have just some minor experience
>with Kaffe and other open source project that use this tool) so, anyone
>that knows libtool better that me can correct me! :-)

I am neither an expert of libtool, and I heard "semi-static" issues
several times on this list. But for the current David's problem, doesn't
following configuration help?
	  --with-staticbin --with-staticlib --with-staticvm

On m68k/{linux,netbsd}, at least libnative etc are looked like to be
linked static.

Kiyo

_______________________________________________
kaffe mailing list
kaffe at kaffe.org
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe