Missing dependencies in bind.tcz.dep for x86_64 (and maybe x86)

[CNK]

A yearly tradition is developing! Almost the same time last year I reported two missing dependencies in bind.tcz. This time, while again trying to run "dig", I found it now also links to libjemalloc.so.2 and libnghttp2.so.14 (jemalloc.tcz & libnghttp2.tcz).

To be clear, I suggest adding these lines to the TC14 x86_64 (and again possibly x86) bind.tcz.dep file:

Code: [Select]

jemalloc.tcz
libnghttp2.tcz


[andyj]

Yes, libnghttp2.tcz does need to be added, but I don't see any dependency on jemalloc in any of the binaries. Which file do you see this on?

[aus9]

hi

Code: [Select]

tc@box:/tmp/tcloop/bind/usr/local/lib$ readelf -d  libisc.so | grep 'NEEDED' | grep libjem
 0x0000000000000001 (NEEDED)             Shared library: [libjemalloc.so.2]
and there may be one more

[andyj]

The problem is that many configure scripts will autodetect if a library is available and link to it if it finds it. If I build bind by itself after a reboot it will have different dependencies than if I build it along with some other extensions at the same time. This is obviously easier to do rather than reboot dozens of times. Bind has three settings for jemalloc: --with-jemalloc=detect (the default), --with-jemalloc=yes/no, and --without-jemalloc. My build script doesn't have any of these right now, which is how it got in unintentionally. The fix will be to say yes or no, the question is which should I do? No means fewer dependencies (the TCL way usually), yes may mean improved performance. If anyone can make a case for yes then I'll add it, otherwise when I refresh it I'll make sure jemalloc isn't required.

[CNK]

Personally I'm just running Dig from the command line so performance is irrelevent to me. But it's people running BIND for DNS on a busy server that these minor optimisations would be aimed at, so their opinion would matter more.