OpenBSD just has a dummy libresolv, that is used for some `legacy' programs
that expect to link against it. It doesn't contain anything useful...
Some configure stuff (kde for instance) detects the presence of libresolv,
and tries to link against it... And of course, libtool detects that there is
Yet another patch, this one pedantic, and mixed with the other one,
since I don't want to bump the package twice.
I've patched configure directly, since patching libtool.m4 makes things
a bit awkward to regenerate (patch to libtool.m4 attached).
On OpenBSD, the ld.so path is /usr/lib, and never
* Thorsten Glaser wrote on Thu, Dec 15, 2005 at 08:10:09PM CET:
Ralf Wildenhues dixit:
The patch is fine as a workaround for above. But regarding upstream
libtool, I'd rather like the fix be done in the right place, in KDEs
configury.
It's not only KDE which barfs at it. Things get worse
The patch is fine as a workaround for above. But regarding upstream
libtool, I'd rather like the fix be done in the right place, in KDEs
configury.
It's not only KDE which barfs at it. Things get worse when you also
have a dummy libdl (libdl functions are in libc), which - out of a
sudden
