[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050803: ntl: relocation error

Chirag,

5.8.2a was compiled under FC1, while 5.8.3a was compiled under FC3.
The Glibc version with FC3 is newer as you note. You should be able to
update your glibc/gcc/g77 packages and run the 5.8.3a binary.

Steve Chiswell
Unidata User Support

>From: "Shukla, Chirag" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200508030542.j735g4jo001557

>Hello,
>
>GEMPAK5.8.3a binary was installed on an old FC2 machine. When `ntl` was
>run, it came up with an error-- 
>
>[gempak@ae206-06 ~]$ ntl
>ntl:relocation error: ntl: symbol __strncpy_chk, version GLIBC_2.3.4 not
>defined in file libc.so.6 with link time reference.
>
>Has anyone come across this error message, or maybe its just me?
>
>
>[gempak@ae206-06 ~]$ ldd `which ntl`
>        libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x00726000)
>        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x00caf000)
>        libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x00c96000)
>        libXp.so.6 => /usr/X11R6/lib/libXp.so.6 (0x00df2000)
>        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00c72000)
>        libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x002b5000)
>        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00b95000)
>        libc.so.6 => /lib/tls/libc.so.6 (0x00a4c000)
>        libdl.so.2 => /lib/libdl.so.2 (0x00b6a000)
>        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00a33000)
>[gempak@ae206-06 ~]$
>
>FC2 machine has 2.6.10-1.771_FC2 kernel. It is a P3-600MHz, 224MB RAM.
>Installed glibc modules:
>glibc-kernheaders-2.4.8.44
>glibc-devel-2.3.3-27.1
>glibc-2.3.3-27.1
>glibc-headers-2.3.3-27.1
>glibc-common-2.3.3-27.1
>
>Is ntl looking for glibc-2.3.4-* ; good time to upgrade glibc/FC? 
>
>
>GEMPAK5.8.2a binary works just fine.
>
>
>Thanks.
>
>Chirag Shukla
>South Dakota State University
>
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.