Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Ed> Suggested fix is to make configure check to see that a library
Ed> is available before trying to use it.
There is no way to do this in general except to try. A system where
the header files can be found with the standard path, but the
libraries cannot, is broken IMO.
Perhaps; but the job of configure is very largely to work around
broken systems.
(if I do invest time in this, I'm not going to leave it at
just the libraries that bug Ed Avis, I'm going to audit all 5400+
lines of configure.in for similar bugs ;-).
Perhaps there is some general way to do it for all libraries that are
used? I dunno, somehow associate each header file name with its
library so that when testing for <foo.h> configure also builds a
small program linked with -lfoo?
I _suspect_ that this would more or less be automatically fixed by a
port of our configure script to autoconf 2.5x.
N.B. All our configure hackers are currently involved with day jobs;
my best guess on ETA for this is Real Soon Now.
OK. I know very little about configure hacking so I think I'll wait
for the autoconf-2.5 port.
--
Ed Avis <ed.avis(a)kbcfp.com>