Alan,
The only way I could prevent it from linking against the system libltdl is to move the system libtool and /usr/lib/liblt* to a directory not in the local path.It seems radiusd is still linked against the system libtool, but this is a development box, and the production box won't have libtool installed.
Is this a bug or am I doing something wrong?
It's most likely a local linker problem. If the compile command has '-lltdl', then it's difficult to know *which* libtool the linker will pick.
Again, the configure options I'm (now) using are:
%configure --prefix=%{_prefix} \
--localstatedir=%{_localstatedir} \
--sysconfdir=%{_sysconfdir} \
--mandir=%{_mandir} \
--with-threads \
--with-thread-pool \
--with-gnu-ld \
--enable-ltdl \
--enable-ltdl-install \
--with-ltdl-install \
--with-ltdl-lib=$RPM_BUILD_DIR/freeradius-snapshot-20021108/libltdl \
--with-ltdl-include=$RPM_BUILD_DIR/freeradius-snapshot-20021108/libltdl
Both the libraries and libtool itself must not be in the path for this to work. I'm not sure if the last two options are necessary...
This certainly isn't the desired approach. Do you have any further recommendations? IOW, it's not purely a linking problem, but 'configure' apparently finds libltdl in the LD_PATH and stops looking once it finds it, despite the options above that tell it not to.
Thanks,
Dave
--
Dave Wreski
Corporate Manager Guardian Digital, Inc.
(201) 934-9230 Pioneering. Open Source. Security.
[EMAIL PROTECTED] http://www.guardiandigital.com
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
