[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnu-radius] CVS version of gnu-radius: .lo files not created

From: Maurice Makaay
Subject: Re: [Bug-gnu-radius] CVS version of gnu-radius: .lo files not created
Date: Sat, 1 Nov 2003 02:33:47 +0100


> > librad_la_OBJECTS = $(am_librad_la_OBJECTS) $(LTLIBOBJS)
> Hmm, this seems a good thing to add to the Makefile.am anyway...

Yes, after adding this, I could compile the libraries correctly. So this 
seems to be a fix for the problem.

> > Another problem I just encountered is that my makeinfo does not understand
> > the @copying tag. I assume that this is a result of an out-dated makeinfo.
> Yep, use at least version 4.3

I upgraded my texinfo package and the info-files could be processed fine now.
So there's no problem here.

BTW Is there somewhere a description of the way gnu-radius should be
compiled from CVS? This should be straight-forward, but I found out that
there can be little bumps on the way. It would be nice to have a list of 
neccessary software and things to take care of for people that want to try
out the CVS version. There's no need in a very long description. Something
like the following would do:

We compile the CVS gnu-radius using the following GNU software:

* autoconf 2.57
* automake 1.7.8
* libtool  1.5 
* gettext  0.12.1 
* texinfo  4.6
* gcc 2.95.1

Short building instructions:

* Run "/bin/sh autogen.sh"
* Run "./configure --enable-maintainer-mode [other options]"
* Run "make debugmod"
* Run "make"

Make sure that your GNU gettext implementation can be found in your 
working path, so the automatic configuration script can find it.

I added last remark about gettext because it can cause some weird problems
when the gettext binaries can't be found. Configure will not really complain
about it, but the Makefile in the po directory will be garbage (the paths to
the gettext utilities will only contain a colon and so running "make" will
fail on this).

Kind regards,

-- Maurice Makaay

reply via email to

[Prev in Thread] Current Thread [Next in Thread]