Re: Configuring without libltdl
In order to generate libltdl.la, it's necessary for me to run make manually. It isn't built automatically for some reason. It looks like making only the following change builds radiusd successfully: make LIBLTDLPATH=$RPM_BUILD_DIR/freeradius-snapshot-20021108/libltdl \ LIBLTDL=$RPM_BUILD_DIR/freeradius-snapshot-20021108/libltdl/.libs/libltdl.a Alan, does this sound reasonable? ldd shows radiusd isn't linked against it, but shouldn't nm show 'ltdl' anywhere in it's output when run against radiusd? dave -- Dave Wreski Corporate Manager Guardian Digital, Inc. (201) 934-9230Pioneering. Open Source. Security. [EMAIL PROTECTED]http://www.guardiandigital.com - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Configuring without libltdl
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'. In order to generate libltdl.la, it's necessary for me to run make manually. It isn't built automatically for some reason. Even once it's built, there is nothing in that file that explicitly specifies to look in ./libs/ for libltdl. Am I still misunderstanding something? Thanks, Dave -- Dave Wreski Corporate Manager Guardian Digital, Inc. (201) 934-9230Pioneering. Open Source. Security. [EMAIL PROTECTED]http://www.guardiandigital.com - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
OS X Darwin build
Hi everyone, Does anyone have a working binary for the Apple's latest Darwin-FreeBSD? I can't seem to get it to build on my Mac. If no one can offer me the binary some pointers for a successful build would be helpful also. Thanks! -MZeek! - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Configuring without libltdl
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
Re: Configuring without libltdl
Or, specify the local libltdl as an *object*, not a *library*. That's pretty much what I said. 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. --enable-ltdl \ --enable-ltdl-install \ --with-ltdl-install \ If you have libltdl already installed, these configuration options will most likely cause problems. I understood this to mean it should install the local ltdl to /usr/lib. So stop playing around with 'configure'. Do what I said. Hack the make rules to link against the included libltdl as an object, not a library. The linker will then NEVER look for -lltdl, so it will NEVER find the one already installed. 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/. dave -- Dave Wreski Corporate Manager Guardian Digital, Inc. (201) 934-9230Pioneering. Open Source. Security. [EMAIL PROTECTED]http://www.guardiandigital.com - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: mysql
Brian Kolaci <[EMAIL PROTECTED]> wrote: > I was amazed so I had to see it for myself. This seems to be a > major bug in mysql. I've grown used to oracle where the behaviour > is correct and doesn't allow the insertion to take place. I agree. That's a bug on the part of MySQL. > I guess a *bad* value as a default would be better than an > empty string. That would confuse a *lot* of people. Though I still think it might be a good idea. In any case, I've added voluminous log messages to rlm_sql. So if the 'op' field is empty or nonsensical, then HUGE numbers of complaints get dumped to the log file. It is my fervent hope that some people will read the error messages, and do something about their misconfigured systems. It would also be good to have more documentation for rlm_sql (there's no 'doc/rlm_sql'), but that's another story. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Configuring without libltdl
Dave Wreski <[EMAIL PROTECTED]> wrote: > 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. Or, specify the local libltdl as an *object*, not a *library*. That's pretty much what I said. > Again, the configure options I'm (now) using are: ... > --enable-ltdl \ > --enable-ltdl-install \ > --with-ltdl-install \ If you have libltdl already installed, these configuration options will most likely cause problems. > --with-ltdl-lib=$RPM_BUILD_DIR/freeradius-snapshot-20021108/libltdl \ Huh? Why are you doing that? That tells 'configure' to go look for libldl, so it calls the linker, which probably finds the libltdl already installed. > 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. So stop playing around with 'configure'. Do what I said. Hack the make rules to link against the included libltdl as an object, not a library. The linker will then NEVER look for -lltdl, so it will NEVER find the one already installed. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Odyssey Client EAP/TLS problem
Here's some more info on the problem I have: The client has a valid certificate, as well as the server. Both of them can validate each others certificate using a valid root certificate. However, the states of the second rad-access-cha packet of the server and the rad-access-req answer packet from the client do not match. The server cannot find a handler for the request (mem.c), more or less ignores this request, and does not receive any other answer, thus sends a rad-access-rej packet. How is the states of the two packets calculated? I guess the certificates are involved here, but they do not seem to be the problem anyway. In the first rad-access-req - rad-access-cha packet pair, the states do match, but I'm not sure if the certs are involved here already. Could the client (Odyssey) be the problem? I highly appreciate any comments. Klaus - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
