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

Again I am suspecious about ncursesw. Please read on.

 I'm beginning to think that something within your ncurses
> installation is wrong (¡expletive! - that would mean Dan was right
> and it is a clfs problem).  Please take a look at all the ncurses
> files in /lib and /usr/lib (the date and time should help you identify
> them), things like libform, libmenu, libncurses, libpanel, libmenu,
> and libcurses.  Normally, each of these should have one static (.a)
> archive in /usr/lib and a series of shared objects (.so*) which
> ultimately point to a binary.  In a straight clfs install, the
> pointing is all done by symlinks, so libncurses.so.5.5 should be the
> binary, and it should be in /lib.  All the libcurses and libncurses
> shared objects in /usr/lib should link to this through a series of
> symlinks.
>
>  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
rwxrwxrwx 1 root root      12 Nov 21 04:50 libcurses.a -> libncurses.a
lrwxrwxrwx 1 root root      25 Nov 21 19:21 libcurses.so ->
../../lib/libncurses.so.5
rw-r--r-- 1 root root  121718 Nov 23 03:59 libform.a
lrwxrwxrwx 1 root root      22 Nov 21 19:22 libform.so ->
../../lib/libform.so.5
rw-r--r-- 1 root root   66694 Nov 23 03:59 libmenu.a
lrwxrwxrwx 1 root root      22 Nov 21 19:21 libmenu.so ->
../../lib/libmenu.so.5
rwxr-xr-x 1 root root  169306 Nov 23 03:59 libncurses++.a
-rw-r--r-- 1 root root  679774 Nov 23 03:59 libncurses.a
lrwxrwxrwx 1 root root      12 Nov 21 19:24 libncurses.so.5 -> libcurses.so
rw-r--r-- 1 root root   26946 Nov 23 03:59 libpanel.a
lrwxrwxrwx 1 root root      23 Nov 21 19:22 libpanel.so ->
../../lib/libpanel.so.5

(No ncursesw.*)

And,

listing of /lib
rwxrwxrwx 1 root root      14 Nov 21 04:50 libform.so.5 -> libform.so.5.5
-rwxr-xr-x 1 root root   71564 Nov 23 03:59 libform.so.5.5
rwxrwxrwx 1 root root      14 Nov 21 04:50 libmenu.so.5 -> libmenu.so.5.5
-rwxr-xr-x 1 root root   34510 Nov 23 03:59 libmenu.so.5.5
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
rwxrwxrwx 1 root root      15 Nov 21 04:50 libpanel.so.5 -> libpanel.so.5.5
-rwxr-xr-x 1 root root   13603 Nov 23 03:59 libpanel.so.5.5

(Again, no ncursesw.*)


Let's do a quicky sanity check and see what the toolchain has to say
about your libraries.

echo 'main(){}' > dummy.c
gcc -Wl,--verbose -lncurses -o dummy dummy.c &> dummy.log
grep ncurses dummy.log
file dummy

Here's what my fresh build just did.

root(chroot):/var/lib/dbnb/build# grep ncurses dummy.log2
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncurses.so failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncurses.a failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncurses.so failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncurses.a failed
attempt to open
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../libncurses.so succeeded
opened script file
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../libncurses.so
opened script file
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../libncurses.so
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncursesw.so failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncursesw.a failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncursesw.so failed
attempt to open /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/libncursesw.a failed
attempt to open
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../libncursesw.so succeeded
-lncursesw (/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../libncursesw.so)
libdl.so.2 needed by
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../libncursesw.so

root(chroot):/var/lib/dbnb/build# file dummy2
dummy2: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for
GNU/Linux 2.6.0, dynamically linked (uses shared libs), for GNU/Linux
2.6.0, not stripped

Obviously, yours may not be 32-bit. But you should get the shared
library by default.

Thanks Dan,
  Here is mine
[EMAIL PROTECTED]: grep curses dummy.log
attempt to open /usr/lib/gcc/x86_64-unknown-linux-gnu/4.1.1/libncurses.so
failed
attempt to open /usr/lib/gcc/x86_64-unknown-linux-gnu/4.1.1/libncurses.a
failed
attempt to open /usr/lib/gcc/x86_64-unknown-linux-gnu/4.1.1/libncurses.so
failed
attempt to open /usr/lib/gcc/x86_64-unknown-linux-gnu/4.1.1/libncurses.a
failed
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


(No libncursesw.* line. I have checked it by opening it using VIM.)

Also.
[EMAIL PROTECTED]: file dummy
dummy: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for
GNU/Linux 2.6.0,
dynamically linked (uses shared libs), for GNU/Linux 2.6.0, not stripped.

From your and Ken's input I think there is some problem with libncursesw.* I
dont seem to have it. This is just a guess.

- Jigslinx
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to