Eli Zaretskii <[EMAIL PROTECTED]> writes: > Btw, this pkg-config thingy is a terrible nuisance. I recently had to > build some package on a RH box, and was amazed to find that all the > ``usual'' tricks of getting `configure' to use non-default include and > library paths simply don't work, because that package's `configure' > script used pkg-config to find all the headers and libraries, and as > you say above, what pkg-config returns cannot be overridden easily. > For example, "LDFLAGS=-L/whatever ./configure" cannot override the > places where the linker run by `configure' looks for libraries. This > means, for example, that if you are an underprivileged user who > installs packages and libraries under ~/, you have no hope of getting > the compiler and the linker to use headers and libraries in those > private directories, since pkg-config doesn't know about them and > keeps pointing the build process to the public directories. > > (If there's a reasonable way of working around this, please let me > know.)
"PKG_CONFIG_PATH=/path/to/dir/with/foo.pc ./configure" _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
