Tom K wrote:
> Ultimately this thing should run from intrd/intramfs, and 
> it can only do that if the libs are compiled statically - right? In 
> ./configure --help, the --enable-static option is the default, but it's 
> always possible some of my sed hacking borked something else - it was 
> fairly crude, as I just wanted to see if I could get it to run. I'll 
> have another stab at it, and see if I can get any further.
>
>   
I've done a bit more research, and it's beginning to make sense now. I 
rebuilt directfb with --enable-static, and the .a files appeared. I'm 
now going to rebuild everything else that ldd /sbin/splashy gives me - 
libpng, zlib, glibc, glib2, and freetype2 - with enable-static, which 
will hopefully give me all the necessary .a files, so I can build it 
without hacking.

Obviously, all this rebuilding of core packages does not do much for 
splashy's prospects on Arch, but now that I've started, I'd like to get 
it running anyway.

Watch this space (that's if anyone is still interested .... :P )

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to