Dave Wreski <[EMAIL PROTECTED]> wrote: > The problem is that apparently without telling configure to not use the > system ltdl, the local libltdl.a that you specified doesn't exist at the > time radiusd is built.
Hmm... that would make sense. If you've already got libltdl installed, there's no need for another one. > The problem is, again, that it's not already installed (or built, for > that matter.) When it is built it isn't even in the directory you've > specified, but rather, it's in ./libltdl/.libs/. There SHOULD be libltdl.la in ./libltdl. The libtool link line should run libtool, which finds that file, and roots through it to discover that the '.a' file is in './libs'. This is the way all of the modules are built, and that works. As for specifying a directory for libltdl, that does NOT affect where the build puts it's files. It only affects where the tools *look*, to find libltdl, during the linking stage. It does NOT affect where the libltdl object files, or archive files go. You're mistaking configure commands for linker and/or install commands. They're completely seperate. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
