On Wed, Jun 21, 2006 at 10:28:12AM -0600, Lin Richardson said: > RE version 1.1.2 > > I'm currious. I have tried compiling 1.1.2 on Solaris 10, OpenBSD 3.9, and > Debian Sid. The ONLY way I have been able to get it working is with the deb > packages. > > I have read exchanges regarding autoconf and libtool issues on the dev > list. The most recent CVS snapshots progress further in the build, but > still result in errors. Any news on when the issues may be resolved, > perhaps a 1.1.3 release? > > I'm not an uber compiler, so I admit I am a bit weak at resolving > compiletime issues. > > Under Solaris 10, my true target platform, I get the following final output > error from the build attempt > (I have already rebuilt the headers under Solaris 10 which is a common > problem when compiling under that OS.) > ... > In file included from dict.c:42: > ../include/libradius.h:316: error: conflicting types for `closefrom' > /usr/include/stdlib.h:193: error: previous declaration of `closefrom' > make[4]: *** [dict.lo] Error 1 > > I am trying to move our enterprise RADIUS to freeradius from a comercial > product, but I need a documented install process that works well. Any > ideas?
<debian maintainer hat on> Take a look at debian/rules in the source package for debian. It is the debian Makefile, and contains anything extra we do to make it build nicely. The closefrom error sounds symptomatic of some of the autotools problems I have been looking at. The relevant lines are: #ifndef HAVE_CLOSEFROM int closefrom(int fd); #endif But clearly there is a system closefrom, so either the macro is undefined, or the configure test missed the system one. Try adding #undef HAVE_CLOSEFROM to src/include/autoconf.h.in, and rerunning the build, at a guess. For this reason and others, I am looking at reworking a bunch of the auto* scripts, and hope they will be acceptable upstream. They all need updating, and some of them can be considerably streamlined, but I don't know how invasive I/you want to be. One of the first things I see is that there are multiple configure scripts in subdirectories, and this is usually not what you want - it's usualy easier to add the tests to the top level configure script and source the config.h from the top level. But again, I've just started looking - there may be reasons (historical or otherwise) for this that I'm not seeing yet. Any tips or pointers greatly appreciated. Take care, -- -------------------------------------------------------------------------- | Stephen Gran | Decision maker, n.: The person in your | | [EMAIL PROTECTED] | office who was unable to form a task | | http://www.lobefin.net/~steve | force before the music stopped. | --------------------------------------------------------------------------
signature.asc
Description: Digital signature
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html