Tom K wrote: > Tom K wrote: > >> Rohan Dhruva wrote: >> >> >>> No, Tom, this is not what ubuntu uses. Ubuntu uses usplash -- which >>> requires special 'hooks' in initrd, unlike splashy. >>> >>> But, imo, someone who uses arch is experienced enough to set up >>> bootsplash .. I hope arch is not having plans of providing it by >>> default, a la frugalware, ubuntu etc etc. >>> >>> Rohan. >>> >>> >> Yeah, big plans - just like the [stable] repo! >> >> Someone who uses Arch would also know that Arch provides nothing by >> default - if you want it, you do it yourself. Just the way it should be, >> if you ask me. :) >> >> >> > Here's what I can see so far. The build aborts on a command that looks > for the following in /usr/lib: > > directfb-0.9.24/systems/libdirectfb_fbdev.a > directfb-0.9.24/wm/libdirectfbwm_default.a > directfb-0.9.24/gfxdrivers/libdirectfb_mach64.a (I've compiled directfb > with that driver only - I expect it would look for all of them with a > full directfb install) > libz.a > libdirectfb.a > libfusion.a > libdirect.a > libpthread.a > libglib-2.0.a > libpng.a > I have directfb, zlib, glibc, glib2, and libpng installed, but I don't > have any of those files. However, I do have files with the same name, > but with extension .so instead of .a. I can run the aborted command > successfully if I change each .a to .so, so that's progress, of a sort. > More progress. I've just run the splashy test command successfully, and the default theme popped up large as life.
That's the good news. The bad news is what I had to do to get there - sed commands to change lib extensions from .a to .so, which I can live with, and ldconfig for /usr/lib/directfb and all its subdirectories, which I can't. 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. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
