Re: .lo files error & making CVS work on FreeBSD

Hi Gerald,

> Heck no, heh. I want to do it the right way and figure out where the
> disparity is. Now I can tell the ports maintainer. This is the first ports
> problem I have run in to with lots and lots of use and abuse in quite a
> while. Out of curiosity, what's your OS of choice for maintaining
> gnu-radius?

GNU/Linux, of course :^) I'm using Slackware, version >= 8.0

> I'm pretty comfortable with just about everything except
> Irix/HP-UX & AIX to some degree.

Yeah, I feel the same way :^)

> To get CVS to (try to) compile on FreeBSD:
[...]
> Reason was gettext and libtool were installing their m4s in aclocal and
> since FreeBSD lets you have more than one version of autoconf everything
> else was in aclocal17.
> 
> "make" complained about not having a libintl.h (which may be documented
> that I needed to provide my own and I missed it)

A possible workaround is to configure radius with --disable-nls option.

> Now I think I'm down to what Maurice ran into:
> 
> http://kod.inch.com/radius/lo_error.txt

Yes, I'm going to handle this after the release.
 
Regards,
Sergey