Re: 2.0.1 configure fails on FreeBSD, patch included

[Tim Auckland]

> > Autoconf can test for most API features directly.  If you know what
> > features you depend on, you should just be able to scan all the
> > plausible library install locations and pick the first one that
> > works, and not worry about picking the *best* one.
> 
> What if you're testing for multiple features?  Could you wind up
> picking two conflicting libraries?  Should you test for multiple
> features of a library or limit yourself to the key feature?

Agreed, using the most basic autoconf macros to test for multiple
features independently could give you conflicting libraries so
instead you should write one macro to test for all the features you
need.

Essentially all autoconf does is test sample code and see if it
compiles (or even runs, if necessary), so you can write a small
code fragment that is representative of the code you actually use,
then try it with all the libraries you've found until you have one
that works.

Tim