peter green wrote: >>> Does anyone know if there is any particular reason that bitlbee uses >>> libresolv.a rather than libresolv.so ? >> Yes; the fact that Ulrich Drepper thought it'd be a good idea to declare >> this API private and unsupported, claiming it's for internal use only, >> even though it's documented in various places already, including IIRC >> O'Reilly's DNS & BIND. > I can see that as a good reason for using the static version in upstream > bitlbee. Nevertheless debian does appear to provide a libresolv.so with > a proper soname and linking against it does seem to give sane > dependencies from dpkg-shlibdeps so maybe it would be a good idea to use > it in the debian packages. Ccing debian-glibc to see if they have an > opinion on the matter.
It looks like you forgot to really Cc them BTW? So yeah, we'd need a libresolv.so that exports these: lib/lib.o: In function `srv_lookup': /home/wilmer/src/bitlbee/devel/lib/misc.c:483: undefined reference to `__res_query' /home/wilmer/src/bitlbee/devel/lib/misc.c:486: undefined reference to `ns_initparse' /home/wilmer/src/bitlbee/devel/lib/misc.c:489: undefined reference to `ns_parserr' I wonder if we could get this fixed in eglibc.. > You could always sed it out of debian/substvars between the call to > dpkg-shlibdeps and dpkg-gencontrol but it's a bit ugly to say the least. > Heh, yeah, that was pretty much my "last resort" solution. But I'm sure I can cook up a proper regex as a workaround somehow to at least return the package to the old situation (before dpkg-shlibdeps detected use of these private symbols). Also, I have a bitlbee branch that uses evdns instead, which also makes the lookups asynchronous, but it's not ready for merging yet. Wilmer. -- +-------- .''`. - -- ---+ + - -- --- ---- ----- ------+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---------------+ +------ ----- ---- --- -- - +
signature.asc
Description: OpenPGP digital signature
