I use SuSE 9.2, with all known updates, on a HP-DL360 G4, which emulates
a 64bit processor system.
The freeradius-package that comes with SuSE does not work on this system
- it fails on loading libraries at start-up:
Module: Library search path is /usr/lib/freeradius
radiusd.conf Failed to link to module 'rlm_exec': rlm_exec.a:
cannot open shared object file: No such file or directory
I have tried SuSE 9.2 on a 32bit system, and there the freeradius-server
that comes with SuSE works well.
Since the freeradius-package that comes with SuSE9.2 does not seem to
work on 64bit architecture, I decided to compile the newest
It fails during compile in
gcc .libs/radiusdS.o -g -O2 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS
-DOPENSSL_NO_KRB5 -Wall -D_GNU_SOURCE -g -Wshadow -Wpointer-arith
-Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -W
-Wredundant-decls -Wundef -I../include -DHOSTINFO=\"\"
-DRADIUSD_VERSION=\"1.0.1\" -o .libs/radiusd radiusd.o files.o util.o
acct.o nas.o log.o valuepair.o version.o proxy.o exec.o auth.o timestr.o
conffile.o modules.o modcall.o session.o xlat.o threads.o smux.o
radius_snmp.o client.o request_list.o mainconfig.o -Wl,--export-dynamic
-L/root/freeradius/freeradius-1.0.1/src/lib -lcrypt -lnsl -lresolv
-lpthread -lcrypto -lssl
/usr/lib/libltdl.so -ldl -lcrypt -Wl,--rpath -Wl,/usr/lib/freeradius
/usr/lib/libltdl.so: could not read symbols: Invalid operation
an my guess is that this happens because the compiler uses
"/usr/lib/libltdl.so" instead of "/usr/lib64/libltdl.so". I can manuallu
run the command with a pointer to the 64-bit catalogue - and this works
Now I have to figure out how to tell GCC to use the 64bit-version of the
libltdl. And here I am lost.
I hope you wont get mad at me for posting this question here :)
I really appreciate any help...
Med vennlig hilsen/Sincerely
Alfred H. Dahl
On SLES 64 there are two versions of the library libpthread.a -
/usr/lib64/libpthread.a & /usr/lib64/nptl/libpthread.a.
What's the difference?
I'm guessing the later maybe implements the Native POSIX Thread Library
while the former uses what? ? (LinuxThreads?, Next Generation POSIX