Alas, it is not that easy. If you have 16 possible libraries you need to link against, it may be that library 5 provides what you were looking for (and need), but library 14 needed something else from library 5 (maybe optional symbols, or an extra library dependency) that it failed to provide. This causes a failure when testing library 14, but the originating problem was in library 5.
Yes, so library 5 is a dependency of library 14. That's what I'm trying to express (in my later post).
However, it is not a *known* (to the configure script developer) dependency. The failure is due to an indirect dependency.
Bob ====================================== Bob Friesenhahn bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
