[Bug-gnu-radius] .lo files error & making CVS work on FreeBSD

[Gerald]

On Wed, 19 Nov 2003, Sergey Poznyakoff wrote:

> Both AM_GNU_GETTEXT and AM_GNU_GETTEXT_VERSION are defined in
> gettext.m4

After much looking at the FreeBSD setup I figured I'd notate the few
changes to compile from CVS (with the auto*, libtool, & gettext from
ports). Package management is our friend.

> To say the truth, I've had quite a lot of unpleasant experience
> with software installed from "ports" on FreeBSD, and this case
> seems to be just another one in the row. Usually I advise
> uninstalling autoconf/automake/gettext and installing them
> from tarballs obtained from ftp.gnu.org. I understand, though,
> that this solution might not be acceptable to you.

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? I'm pretty comfortable with just about everything except
Irix/HP-UX & AIX to some degree.

To get CVS to (try to) compile on FreeBSD:

Prereq: making sure the correct versions of
automake;autoconf;libtool;and gettext are installed.

- cd /usr/local/share/
- cp aclocal/* aclocal17/ # checked to make sure there were no conflicting
  m4s and made a backup beforehand
- rm -r aclocal # After making backup of it
- ln -s /usr/local/share/aclocal17 /usr/local/share/aclocal # hardcoded
  paths in the m4s are ugly...this was to compensate for it.

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)

cp /usr/local/include/libintl.h ./include

I now see the port maintainer for gnu-radius passes this to configure:
CONFIGURE_ARGS+=--with-include-path="${LOCALBASE}/include/" \
                --with-lib-path="${LOCALBASE}/lib/"

Now I think I'm down to what Maurice ran into:

http://kod.inch.com/radius/lo_error.txt

The other thing I was going to ask is if you had the cvs commit messages
being delivered anywhere? If it's a per request thing, consider this my
request that my E-mail address receive any commit msgs in E-mail.

Mailings of CVS commits remind me to update the source when a change is
made. Most make a separate mailing list for just CVS commits.

Gerald