Bill Moseley writes: > If I use AC_CHECK_LIB does configure try to *run* the program? No. > What's happening is configure and make run fine, but ldd shows "not > found" for libz's runtime linkage. Build-time linker path and run-time linker path are two different things. > I'm linking with zlib which is installed in /usr/local/lib, but it seems > that on this machine (Solaris 2.6) that /usr/local/lib is not part of > the default search path. That is the normal setup on Solaris, and indeed the zlib problem is also quite "normal" on Solaris. > This causes confusion because configure is saying libz is found and then > make check fails saying libz is not found. Then you need to teach make check about the run-time linker path. > Another thing that is confusing (and I'm not sure if it's related to why > configure is not failing the libz check) is that the problem only > happens when using a --prefix setting. That sounds pretty weird, but the problem would probably be with your makefiles. > It would be nice if configure would catch this. But I'm not sure if > it's because configure is not actually running the test program for > zlib, or if configure is using a different -R when linking the test > program vs. linking the application. configure cannot run any programs (leaving aside the whole cross-compilation issue), or at least it won't generally get reliable information out of that process, because the environment in which you build the program is not necessarily the one in which you plan to run the program. Making that requirement is impractical in many cases. -- Peter Eisentraut peter_e@xxxxxxx
