topic Re: nmap install , symbol not found error in Operating System - HP-UX

nmap install , symbol not found error

kzhang_1 — Wed, 07 Mar 2007 10:08:01 GMT

I installed nmap tool on my itanium rx4640.
and get these error.
Anyone here can help me for this problem.
I installed all dependencies, and set SD_l

/tmp/gcc#ldd -r /usr/local/bin/nmap
libpcre.so => /usr/local/lib/hpux32/libpcre.so
libpcap.so => /usr/local/lib/hpux32/libpcap.so
libssl.so => /usr/local/lib/hpux32/libssl.so
libcrypto.so => /usr/local/lib/hpux32/libcrypto.so
libnm.so => /usr/lib/hpux32/libnm.so
libstdc++.so => /usr/local/lib/libstdc++.so
libunwind.so.1 => /usr/lib/hpux32/libunwind.so.1
libm.so.1 => /usr/lib/hpux32/libm.so.1
libc.so.1 => /usr/lib/hpux32/libc.so.1
libc.so.1 => /usr/lib/hpux32/libc.so.1
libdl.so.1 => /usr/lib/hpux32/libdl.so.1
libc.so.1 => /usr/lib/hpux32/libc.so.1
libuca.so.1 => /usr/lib/hpux32/libuca.so.1
symbol not found: __udivsi3 (/usr/local/bin/nmap)
symbol not found: __divsi3 (/usr/local/bin/nmap)
symbol not found: __modsi3 (/usr/local/bin/nmap)
symbol not found: __umodsi3 (/usr/local/bin/nmap)
symbol not found: __udivdi3 (/usr/local/lib/libstdc++.so)
symbol not found: __udivsi3 (/usr/local/lib/libstdc++.so)
symbol not found: __divsi3 (/usr/local/lib/libstdc++.so)

Re: nmap install , symbol not found error

Steven E. Protter — Wed, 07 Mar 2007 10:09:44 GMT

Shalom,

It would be helpful to know whether you installed the depot version or not. I have found the depot version to be very unreliable and suggest you try compiling nmap from the source code.

SEP

Re: nmap install , symbol not found error

kzhang_1 — Wed, 07 Mar 2007 10:17:34 GMT

Thanks for your fast reply, Steven
I have a old version running on the other machine works fine.
I will recompile it on this machine.
Thanks again

Re: nmap install , symbol not found error

Dennis Handly — Wed, 07 Mar 2007 18:24:04 GMT

Hmm, I keep seeing these unsats. I'm not sure how anyone can make a depot with these unsat errors and not notice the product doesn't run?? (The executable should have been linked with libgcc.a.)

About the only thing that could make sense is that these symbols were in one of the above shlibs when they made them but not on the versions on your system.