You can link them -static, which avoids all the ld.so and libs
	issue. If space is an issue you should probably look at using
	crunchgen, which avoids the extra copies of all the library
	functions. 

	From the manpage:

     A crunched binary is a program made up of many other programs linked to-
     gether into a single executable.  The crunched binary main() function de-
     termines which component program to run by the contents of argv[0].  The
     main reason to crunch programs together is for fitting as many programs
     as possible onto an installation or system recovery floppy.
	
	If you look in ~src/distrib/... you can fidn some examples of
	crunchgen usage (maybe ~src/distrib/sparc/ramdisk.sysinst)



		David/absolute

 -=-  "I know its not the right thing, and I know its not the good thing"  -=-

On Thu, 13 May 1999, Bruce Martin wrote:

> Hi All,
> 
> I want to create a diskless system on the arm32, which I
> have got working by building a ramdisk image into the kernel
> and loading md0 at boot time. This works fine - however, I
> have noticed that when we load our own gcc compiled
> programs, we also need to put ld.so, libc and other files
> onto the ramdisk, which takes up valuable space - is there
> any way of compiling or otherwise so that programs are
> "standalone"?
> 
> Thanks
>   Bruce
>