Re: [Cpu-users] CPU 1.3.99

[Blake M. <ma...@db...>]

Run ./bootstrap to get everything configured. In the README file are
instructions for compiling, including what versions of the autotools need to
be installed. Keep in mind that you now _must_ run configure with ./configure
--with-ldap to get the ldap plugin compiled.

-Blake

Whatchu talkin' 'bout, Willis?
> >Date: Mon, 10 Feb 2003 15:21:06 -0500
> >From: Blake Matheny <bma...@pu...>
> >To: cpu...@li...
> >Subject: [Cpu-users] CPU 1.3.99
> >
> >Hello List,
> >I'm not actually sure if anyone is still on this or not :-) It's been 
> >almost a
> >year since any fresh code has been written, but I refuse to let CPU become
> >another abandoned free software project! Having said that, this weekend I
> >tried to do something about it and completely rewrote CPU. It was a mess,
> >and not something that I would have wanted to contribute to. The 'new' 
> >version
> >is currently only available via cvs, under the directory 'cpu'. The TODO 
> >file
> >has been included below. Please, if you can donate time or energy to help 
> >out,
> >including testing, please do. Thanks.
> >
> >------------------------------------------------------------------------------
> >There is a lot to do in order to get CPU to a place where I can put it to 
> >rest
> >for good. I decided to rewrite all of the code, which while this was a good
> >idea, doing it in a weekend may not have been. As a result, there are a few
> >bugs.
> >
> >I rewrote the system so that it would be more attractive for someone to 
> >pickup
> >and continue to maintain. If you are interested (or will be after I finish
> >with the fixes below) please contact me.
> >
> >Here are some of the features that CPU 1.3.99 has that previous versions 
> >did
> >not, and some of the features that are still missing:
> >
> >New Features
> >* Code is extremely modular, meaning people can write back-ends easily for 
> >any
> >  kind of system by just exporting CPU_init in their code. This also makes 
> >  it
> >  easy for people to include code already written from other projects.
> >* I'm not so embarrassed to have written it
> >* New configuration file format allows multiple authentication methods to 
> >be
> >  used
> >* Modular design allows you to specify which back-end to administer 
> >through a
> >  command line switch which will then load the appropriate module. All 
> >  command
> >  line options are specific to the back-end you are administering
> >* Some API functionality to encourage people to write some new back-ends.
> >* Rewrote build system
> 
> I couldn't get this to build without a src/include/config.h.in file. 
> Are there "developer" build instructions somewhere?  Minimum toolchain 
> requirements?  I did:
> libtoolize
> aclocal
> autoconf
> automake
> ./configure
> make
> ...which died because "VERSION" wasn't defined.  I fixed that, then it 
> died because "HAVE_BZERO" wasn't defined.  I fixed that, and it built. 
> But now the LDAP plugins don't build.  Is it because "HAVE_LDAP" isn't 
> set in automake?  How do I set it?
> Thanks,
> John Dalbec
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your  SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> Cpu-users mailing list
> Cpu...@li...
> https://lists.sourceforge.net/lists/listinfo/cpu-users

-- 
Blake Matheny           "... one of the main causes of the fall of the
ma...@db...      Roman Empire was that, lacking zero, they had
http://www.dbaseiv.net   no way to indicate successful termination of
http://ovmj.org/GNUnet/  their C programs." --Robert Firth