I've been chasing down why the ramdisk I built with the glibc 2.2.2 libraries didn't work. It seems to me that the error reported is misleading as I'm sure the library was in the path and is found. It seems that libdb, that the working ramdisk uses, is no longer part of the glibc package and you have to get it separately. When I couldn't find it I was still using the old one. My guess is that the error is being reported in the library that is making the call to libdb but as I don't know much about the way these libraries work it is only a guess. Thoughts anyone? Does anyone know a way I can find out more exactly which call is failing and where it is being made. Schulttz from Hogans heros summed up my knowledge of this area succinctly; "I know nothing!" I've managed to get the source and will probably try and build it next week to see if that helps. It will be a bit awkward as the configure script doesn't seem to produce a makefile suitable for a cross compiling environment. Has anyone out there had to do this and have any words of wisdom before I fall into the same pits you've already fallen into? Or perhaps you know where there is a ramdisk already holding glibc that works. jon _______________________________________________ http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm Please visit the above address for information on this list.
