"John Padula" <[EMAIL PROTECTED]> wrote: > Maybe I wasn't clear, but the configure-make sequence on the new > machine was done with a fresh 0.2 TAR file, so I tried to keep things > consistent and only used CC throughout. Yes, but the configure script *may& pick up gcc instead of cc. > I examined the machine that all this initially worked on and tracked > down this include file (and the associated library) as belonging to > the "KDE - X11 Windowing Environment". The second machine did not > have this installed - though it did have a Solaris equivalent (called > Gnome). I pointed my paths to the Gnome directories, did a "make > clean" and tried again. It still failed! Ultimately, I added the > paths to the gnome area by hand to the libtool and it worked!! Not > sure why these weren't picked up from my environment. I even fixed > LD_LIBRARY_PATH to point to these...?! If 'configure' picks up the libraries, then a normal 'cc' should pick them up, too. The 'configure' script finds where gdbm is, and if it's in a non-standard place, updates rlm_counter/Makefile to point to them. > Don't know how much of this is useful information that might prevent > others from spinning their wheels for 3+ hours trying to get this > resolved, but there you have it. Doing 'configure' on one machine, and a 'make' on another, usually causes this kind of problem. I don't know if that's what you did, though. > By the way - regarding the $PGROOT problem - to get around this, I > copied the test from the 0.2 "configure" script. Basically, the > line is: > Not sure why this was changed from what was in 0.2, but maybe it can > be changed back. Hmm... I'll have to take a look at that again. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
