On Tue, 22 Feb 2005, Bob Friesenhahn wrote:
On Tue, 22 Feb 2005, Hugh Sasse Staff Elec Eng wrote:
totally wrong though, since failure to detect a header or library could actually be due to an earlier error in the configuration process (config.log needs to be carefully inspected).
Tsort. If an earlier thing fails for a given branch of dependencies then tests for things later in that branch will fail. It doesn't
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).
This is actually a pretty common problem.
Similar things occur when testing header files.
Bob
Hugh
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
