On 08/11/2018 01:18 PM, Tom Lane wrote:
In a moment of idle curiosity, I tried to build PG --with-libxml on NetBSD-current (well, mostly current, from May or so). The configure script blew up, complaining that it couldn't execute a test program. Investigation showed that xml2-config reports this: $ xml2-config --libs -Wl,-R/usr/pkg/lib -L/usr/pkg/lib -lxml2 -L/usr/lib -lz -L/usr/lib -llzma -L/usr/lib -lm and we're only paying attention to the -L switches out of that. So we successfully link to /usr/pkg/lib/libxml2.so, but then execution fails for lack of rpath pointing at /usr/pkg/lib. We could fix this by teaching configure to absorb -Wl,-R... switches into LDFLAGS from xml2-config's output, and that seems to make things work, but I wonder whether we should or not. This seems like a new height of unfriendliness to non-default packages on NetBSD's part, and it's a bit hard to believe the behavior will make it to a formal release. I don't see any comparable behavior on FreeBSD for instance --- it puts packages' libraries into /usr/local/lib, but that seems to be searched automatically without additional switches beyond -L. Don't have an easy way to check things on OpenBSD.
OpenBSD-6.3's "xml2-config --libs" doesn't contain any rpath settings, it's pretty much like the one on my (fairly old) FBSD machine, as you describ4ed above.
cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
