On Wed, Dec 06, 2006 at 01:44:42PM +0530, jignesh gangani wrote: > Hi, > > >From memory, you are on pure64 ? I've just fired up my pure64 > >amd64 and gpm-1.20.1 builds for me with the clfs patches and > >instructions. That system is clfs-1.0.0 with ncursesw. > > Yes Ken, I am on Pure64. What do you mean by clfs patches?. I have applied > following patches to GPM- > > gpm-1.20.1-segfault-1.patch > gpm-1.20.1-silent-1.patch > Yes, that's right - it was a typo for 'blfs-patches' > Again I am suspecious about ncursesw. Please read on. > I only mentioned ncursesw because I've seen similar breakage from my attempts to use it in clfs (we do ncurses slightly differently from what is now in lfs, and some of the detail is easy to break). If you followed the clfs book, you won't have libncursesw. [...] > >> For each of the libraries I listed, first verify that there is a > >> binary .so.5.5 in /usr/lib with a size in the tens or hundreds of > >> kilobytes (instead of a file with only a few bytes containing a link > >> instruction), then verify that each of the other .so* variants in /lib > >> and /usr/lib has an unbroken chain of symbolic links to get to the > >> binary. > > > Here is the listing of both /lib and /usr/lib > > listing of /usr/lib [snipping to only ncurses.so variants ] > lrwxrwxrwx 1 root root 25 Nov 21 19:21 libcurses.so -> > ../../lib/libncurses.so.5 > lrwxrwxrwx 1 root root 12 Nov 21 19:24 libncurses.so.5 -> libcurses.so > > (No ncursesw.*) > > And, > > listing of /lib > lrwxrwxrwx 1 root root 17 Nov 21 04:50 libncurses.so.5 -> > libncurses.so.5.5 > -rwxr-xr-x 1 root root 395130 Nov 23 03:59 libncurses.so.5.5 > > (Again, no ncursesw.*) The problem was with libncurses, where gpm tried to link in the .a instead of the .so. - I was going to say that your symlinks all point to /lib/libncurses.so.5.5 but in fact I think I can see the problem - the search starts in /usr/lib where there is a .so.5 but *not* a plain libncurses.so : any app that tries to link to libncurses.so.5 will find the shared object, but anything that tries to link to just libncurses will not find a .so and will fall back to the .a which is ok for an application but useless for a shared library on this architecture.
> attempt to open > /usr/lib/gcc/x86_64-unknown-linux-gnu/4.1.1/../../../../lib/libncurses.so > failed > attempt to open > /usr/lib/gcc/x86_64-unknown-linux-gnu/4.1.1/../../../../lib/libncurses.a > succeeded If I can count the '../' correctly, that shows it failing to open /usr/lib/libncurses.so - try ln -svf ../../lib/libncurses.so.5 /usr/lib/libncurses.so (the second of the symlinks we add in the x86_64-64 clfs-1.0.0 book) Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
