Alan:
Thanks for the speedy response.
> Of course, if you use 'gcc' when running 'configure',
> and 'cc' for the compile, then that would explain some
inconsistencies.
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.
I've since loaded GCC on the target machine and (1) the horrible
compiler warnings
were cut down significantly (not suprising - Solaris' CC is usually
pickier) and (2) the
gdbm errors continued. So, at least gcc did not fix the path problem.
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...?!
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.
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:
if test $PGROOT ; then
IS_LOCAL=1
versus
if test -d $PGROOT ; then
IS_LOCAL=1
and later:
if test $PGROOT && test IS_LOCAL ; then
versus
if test -d $PGROOT && test "x$IS_LOCAL" != "x" ; then
Not sure why this was changed from what was in 0.2, but maybe it can be
changed back.
Hope all that helps. I'll finally test the dynamic IP allocation fix
you made a few weeks ago
and let you know how it goes.
Thanks,
JohnP
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
