Re: Symantec Netbackup under 7.1 - Undefined symbol
On Fri, Apr 03, 2009 at 10:15:50PM +0100, Vincent Hoffman wrote: > > > Fair point, I had a bit more of a think, I'd now guess that it looks > like a 32/64 bit problem, its a 32bit binary on a 64 bit system and its > /libexec/ld-elf.so.1 complaining not /libexec/ld-elf32.so.1 whch is odd. > do you have the lib32 compat stuff installed, does > /libexec/ld-elf32.so.1 exist on your system? if not you can add it via > sysinstall -> configure -> Distributions -> lib32. Hi, Here's what the binaries in question point to: # ldd ./bplist ./bplist: libkvm.so.2 => /usr/local/lib32/compat/libkvm.so.2 (0x280d1000) libstdc++.so.4 => /usr/local/lib32/compat/libstdc++.so.4 (0x280d7000) libm.so.3 => /usr/local/lib32/compat/libm.so.3 (0x281b4000) libc.so.5 => /usr/lib32/libc.so.5 (0x281cf000) # All of these libraires exist: # ls -l /libexec/ld-elf32.so.1 -r-xr-xr-x 1 root wheel 170944 Apr 2 20:16 /libexec/ld-elf32.so.1 # ls -l /usr/local/lib32/compat/libkvm.so.2 -r--r--r-- 1 root wheel 24957 Mar 30 13:19 /usr/local/lib32/compat/libkvm.so.2 # ls -l /usr/local/lib32/compat/libstdc++.so.4 -r--r--r-- 1 root wheel 1102049 Mar 30 13:19 /usr/local/lib32/compat/libstdc++.so.4 # ls -l /usr/local/lib32/compat/libm.so.3 -r--r--r-- 1 root wheel 126743 Mar 30 13:19 /usr/local/lib32/compat/libm.so.3 # ls -l /usr/lib32/libc.so.5 -r--r--r-- 1 root wheel 1047956 Mar 24 14:32 /usr/lib32/libc.so.5 # So it's even more strange to me that "/libexec/ld-elf.so.1" complains about the undefined symbol "__h_error" Is there any way to track this down furhter? BTW, note I've got /usr/ports/misc/compat5x installed which "pkg_info" displays as " compat5x-amd64-5.4.0.8_9" -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Symantec Netbackup under 7.1 - Undefined symbol
On 3/4/09 20:39, Ewald Jenisch wrote: > On Fri, Apr 03, 2009 at 11:08:50AM -0600, Tim Judd wrote: > > >>> This would lead me to think you need the port misc/compat5x installed. >>> I havent any experience of netbackup though. >>> >> I agree with this statement, since it's clearly listed as it was compiled >> FOR FreeBSD 5.3 >> >> The compatXy packages are for what I think I remember reading of kernel >> system calls. I think there's a package/port for the userland utilities >> too.. misc/compat5x >> >> However I'm a smidge confused. The option that exists in the kernel and the >> misc/compat5x port -- do they accomplish the same thing, or is it really >> "kernel" and "userland" peices? >> > > The kernel options provide kernel level compatability, the port gives library (userland) compatability, dynamicly linked apps will need the librarys. > Hi, > > I've got both compat5x and compat5x installed on the machine in question: > > $ pkg_info -cx compat > Information for compat4x-i386-5.3_9: > Comment: > A convenience package to install the compat4x libraries > > Information for compat5x-amd64-5.4.0.8_9: > Comment: > A convenience package to install the compat5x libraries > $ > > In my kernel I've got the following compat-related options enabled (default): > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options COMPAT_FREEBSD5 # Compatible with FreeBSD5 > options COMPAT_FREEBSD6 # Compatible with FreeBSD6 > > Please note, that the error message posted in my original email comes > from /libexec/ld-elf.so.1 > > -ewald > Fair point, I had a bit more of a think, I'd now guess that it looks like a 32/64 bit problem, its a 32bit binary on a 64 bit system and its /libexec/ld-elf.so.1 complaining not /libexec/ld-elf32.so.1 whch is odd. do you have the lib32 compat stuff installed, does /libexec/ld-elf32.so.1 exist on your system? if not you can add it via sysinstall -> configure -> Distributions -> lib32. Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Symantec Netbackup under 7.1 - Undefined symbol
On 4/3/09, Ewald Jenisch wrote: > On Fri, Apr 03, 2009 at 11:08:50AM -0600, Tim Judd wrote: > >> > This would lead me to think you need the port misc/compat5x installed. >> > I havent any experience of netbackup though. >> >> >> I agree with this statement, since it's clearly listed as it was compiled >> FOR FreeBSD 5.3 >> >> The compatXy packages are for what I think I remember reading of kernel >> system calls. I think there's a package/port for the userland utilities >> too.. misc/compat5x >> >> However I'm a smidge confused. The option that exists in the kernel and >> the >> misc/compat5x port -- do they accomplish the same thing, or is it really >> "kernel" and "userland" peices? > > Hi, > > I've got both compat5x and compat5x installed on the machine in question: > > $ pkg_info -cx compat > Information for compat4x-i386-5.3_9: > Comment: > A convenience package to install the compat4x libraries > > Information for compat5x-amd64-5.4.0.8_9: > Comment: > A convenience package to install the compat5x libraries > $ > > In my kernel I've got the following compat-related options enabled > (default): > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options COMPAT_FREEBSD5 # Compatible with FreeBSD5 > options COMPAT_FREEBSD6 # Compatible with FreeBSD6 > > Please note, that the error message posted in my original email comes > from /libexec/ld-elf.so.1 With ldd(1) you could check on what libraries it depends, alternatively you could try LD_PRELOAD with your own written lib specially designed to workaround this problem(in theory). -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Symantec Netbackup under 7.1 - Undefined symbol
On Fri, Apr 03, 2009 at 11:08:50AM -0600, Tim Judd wrote: > > This would lead me to think you need the port misc/compat5x installed. > > I havent any experience of netbackup though. > > > I agree with this statement, since it's clearly listed as it was compiled > FOR FreeBSD 5.3 > > The compatXy packages are for what I think I remember reading of kernel > system calls. I think there's a package/port for the userland utilities > too.. misc/compat5x > > However I'm a smidge confused. The option that exists in the kernel and the > misc/compat5x port -- do they accomplish the same thing, or is it really > "kernel" and "userland" peices? Hi, I've got both compat5x and compat5x installed on the machine in question: $ pkg_info -cx compat Information for compat4x-i386-5.3_9: Comment: A convenience package to install the compat4x libraries Information for compat5x-amd64-5.4.0.8_9: Comment: A convenience package to install the compat5x libraries $ In my kernel I've got the following compat-related options enabled (default): options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 Please note, that the error message posted in my original email comes from /libexec/ld-elf.so.1 -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Symantec Netbackup under 7.1 - Undefined symbol
On Fri, Apr 3, 2009 at 9:01 AM, Vincent Hoffman wrote: > On 3/4/09 13:28, Ewald Jenisch wrote: > > Hi, > > > > This question is not purely about FreeBSD itself, but about getting > > Symantec Netbackup (formerly Veritas) running under FreeBSD. > > > > First of all FreeBSD is supported directly; there's a native > > commandline client for FreeBSD that supports 7.0. > > > > I'm using FreeBSD 7.1 (fresh kernel/system as per today), AMD64 > > architecture with Symanted NetBackup 6.5.3.1. > > > > Installation runs OK, but when I try to run any of the Symantec > > programs I get the following error: > > > > # ./bpclimagelist > > /libexec/ld-elf.so.1: ./bpclimagelist: Undefined symbol "__h_error" > > # file bpclimagelist > > bpclimagelist: ELF 32-bit LSB executable, Intel 80386, version 1 > (FreeBSD), for FreeBSD 5.3, dynamically linked (uses shared libs), > FreeBSD-style, not stripped > > # > > > > > This would lead me to think you need the port misc/compat5x installed. > I havent any experience of netbackup though. I agree with this statement, since it's clearly listed as it was compiled FOR FreeBSD 5.3 The compatXy packages are for what I think I remember reading of kernel system calls. I think there's a package/port for the userland utilities too.. misc/compat5x However I'm a smidge confused. The option that exists in the kernel and the misc/compat5x port -- do they accomplish the same thing, or is it really "kernel" and "userland" peices? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Symantec Netbackup under 7.1 - Undefined symbol
On 3/4/09 13:28, Ewald Jenisch wrote: > Hi, > > This question is not purely about FreeBSD itself, but about getting > Symantec Netbackup (formerly Veritas) running under FreeBSD. > > First of all FreeBSD is supported directly; there's a native > commandline client for FreeBSD that supports 7.0. > > I'm using FreeBSD 7.1 (fresh kernel/system as per today), AMD64 > architecture with Symanted NetBackup 6.5.3.1. > > Installation runs OK, but when I try to run any of the Symantec > programs I get the following error: > > # ./bpclimagelist > /libexec/ld-elf.so.1: ./bpclimagelist: Undefined symbol "__h_error" > # file bpclimagelist > bpclimagelist: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), > for FreeBSD 5.3, dynamically linked (uses shared libs), FreeBSD-style, not > stripped > # > > This would lead me to think you need the port misc/compat5x installed. I havent any experience of netbackup though. Vince > Here are my questions: > > o) Anybody out there in the FreeBSD community who is using the > NetBackup client successfully under FreeBSD? > > o) What does the above error message mean? Is it that the executable > (bpclimagelist in this case) is referencing a symbol that isn't > contained in ld-elf.so.1? > > o) Any ideas on how to track this down further? > > Thanks much in advance for your help, > -ewald > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
