alliance-support '1998
libc5 obscure problem? SOLVED


Jorge JUAN CHICO (jjchico@imse.cnm.es)
Wed, 23 Dec 1998 12:44:48 +0100 (MET)

Finally I found the solution for the problem I myself sent a few days before. graal and dreal expect a /usr/tmp directory to exist, which is not true for Debian 2.0. I just linked it to /tmp and they work fine now: # ln -s /tmp /usr/tmp I found the problem using the strace program. Maybe the graal source code could be changed to access /tmp and adhere the FHS. The problem with scilab must be different as this didn't work with it. Hopping to be useful, Jorge. ---------- Forwarded message ---------- Date: Wed, 16 Dec 1998 20:02:08 +0100 (MET) From: Jorge JUAN CHICO <jjchico@imse.cnm.es> To: alliance-support@asim.lip6.fr Subject: libc5 obscure problem? (fwd) ---------- Forwarded message ---------- Date: Wed, 16 Dec 1998 19:51:09 +0100 From: Jorge JUAN CHICO <jjchico@imse.cnm.es> Newsgroups: linux.debian.user Subject: libc5 obscure problem? I run hamm on two boxes and have the same problem: some x programs compiled against libc5 don't work. They spend some seconds (doing initialization or whatever) and then silently exit without any error message. I have no a clue about what the problem is. I've observed the problem with scilab (a deb package) and the X-programs (graal and dreal) of the Alliance 3.2b environment (a set of tools to do IC design http://asim.lip6.fr/alliance). The most clear example is scilab (which binary is scilex), which comes with hamm (and bo). Some data: - both programs run perfectly under bo. - ldd gives the right links to libc5 libraries. $ ldd `locate scilex` libdl.so.1 => /lib/libdl.so.1 (0x4000b000) libXaw.so.6 => /usr/lib/libc5-compat/Xaw3d/libXaw.so.6 (0x4000e000) libXmu.so.6 => /usr/lib/libc5-compat/libXmu.so.6 (0x40061000) libXt.so.6 => /usr/lib/libc5-compat/libXt.so.6 (0x40073000) libXext.so.6 => /usr/lib/libc5-compat/libXext.so.6 (0x400b5000) libSM.so.6 => /usr/lib/libc5-compat/libSM.so.6 (0x400c0000) libICE.so.6 => /usr/lib/libc5-compat/libICE.so.6 (0x400c9000) libX11.so.6 => /usr/lib/libc5-compat/libX11.so.6 (0x400de000) libncurses.so.3.0 => /lib/libncurses.so.3.0 (0x4017c000) libf2c.so.2 => /usr/lib/libf2c.so.2 (0x401b8000) libm.so.5 => /lib/libm.so.5 (0x401d6000) libc.so.5 => /lib/libc.so.5 (0x401df000) libc.so.6 => /lib/libc.so.6 (0x4029d000) ld-linux.so.2 => /lib/ld-linux.so.2 (0x40342000) $ ldd `which graal` libSM.so.6 => /usr/lib/libc5-compat/libSM.so.6 (0x4000b000) libICE.so.6 => /usr/lib/libc5-compat/libICE.so.6 (0x40014000) libXt.so.6 => /usr/lib/libc5-compat/libXt.so.6 (0x40029000) libX11.so.6 => /usr/lib/libc5-compat/libX11.so.6 (0x4006b000) libm.so.5 => /lib/libm.so.5 (0x40109000) - The same problem in both systems (P166 upgraded from bo to hamm and PII 266 new hamm instalation) - Other libc5 programs run OK - A custom compilation of one aplication (graal) against libc6 have the same problem. $ ldd ./graal libXm.so.1 => /usr/X11R6/lib/libXm.so.1 (0x4000f000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40114000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x4011d000) libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40134000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4017c000) libm.so.6 => /lib/libm.so.6 (0x4021f000) libc.so.6 => /lib/libc.so.6 (0x40238000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) I desperately need some help as I pretend that about 100 alumns install Debian to run de design environmen. Thanks in advance. Jorge. ---------- End Forwarded message ---------- Any clue? Jorge.

 



Alliance Web Site © 1997, 2002 ASIM/LIP6/UPMC, page maintained by Czo [Olivier Sirol] , last updated on 22 March 2001.