I've got a test in a configure script that runs like this: ... checking for MD5Init gcc -o conftest -g -O2 -Wall -Wcast-qual -Wmissing-prototypes -Wpointer-arith -Wshadow -Wstrict-prototypes conftest.c -lmd5 -lelf >&5 conftest.c:51: warning: function declaration isn't a prototype conftest.c:58: warning: function declaration isn't a prototype conftest.c:66: warning: function declaration isn't a prototype /usr/bin/ld: warning: libssl.so.5, needed by /usr/lib/gcc/i386-redhat-linux/4.1.1/../../../libmd5.so, not found (try using -rpath or -rpath-link) and this test therefore succeeds, as gcc/ld is treating this like a warning instead of an error. The target system is a Debian system, as I understand it. Suggestions on how I can write this test better? H _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
