On 8/23/06, Stephen Gran <steve@lobefin.net> wrote:
I _think_ that it blows up in rlm_exec because it's the first module that uses a symbol from the radiusd binary (as opposed to a library). I also think this has something to do with the mystery that is OS X's linker namespaces. Beyond that, I'm starting to flounder. I have no Mac machine handy to test these assumptions on (and I'm not even sure how I would test the second one), so I can't really say much more, sorry.
In terms of accessing binaries or libs, would it have anything to do with permissions? Is that possible? Does anyone have any suggestions on using, perhaps, a previous version? Or some experience with using a certain version of the OSX developer tools for compiling? I know these questions are a bit obtuse, but I'd like help in even a direction to pursue.
If you don't actually need the modules that cause problems, you can comment the references out and see if that gets you by.
OK, where to do that? In the original make file?
Good luck, and sorry, but without something to test on, I'm out of ideas.
Thanks, I'll need the luck, I guess. Hey, for grins, I compiled and ran version 1.0.5. It makes it through the compile with no problems and when run, I get: unix: radwtmp = "/usr/local/var/log/radius/radwtmp" unix: usegroup = no unix: cache_reload = 600 Module: Instantiated unix (unix) radiusd.conf[10] Failed to link to module 'rlm_eap': dlopen(rlm_eap.so, 9): image not found So, similar problem, different module. Am I on to something here? Can someone tell me what I am on to? :) Michael Check