/usr/sbin/rndc-confgen: error while loading shared libraries: libdns.so.11: cannot open shared object file: No such file or directory This occurs when emerging is almost done, after putting files into place but before the post-emerge information. Mentioned in there was: * If you like to run bind in chroot AND this is a new install OR * your bind doesn't already run in chroot, simply run: * `ebuild /var/db/pkg/net-dns/bind-9.2.3/bind-9.2.3.ebuild config` I ran the command mentioned, however this happened: ad80-126-113-115 root # ebuild /var/db/pkg/net-dns/bind-9.2.3/bind-9.2.3.ebuild config * * Setting up the chroot directory...chown: failed to get attributes of `/chroot/dns/etc/bind/rndc.key': No such file or directory Done. * * Add the following to your root .bashrc or .bash_profile: * alias rndc='rndc -k /chroot/dns/etc/bind/rndc.key' * Then do the following: * source /root/.bashrc or .bash_profile * ad80-126-113-115 root # so I guess there's something wrong with the libraries?
Is this a new install, or an upgrade? If so, from what version of BIND?
It's a new install, Stewart.
So, what happens now?
Note: this also happens when trying to start bind. /usr/sbin/named: error while loading shared libraries: libdns.so.11: cannot open shared object file: No such file or directory Stewart or others, could you help me with this please? I want to run a nameserver.
I don't know why yet but I did this lastnight and had the same problem... I emerged bind a 2nd time and it seemed to install everything properly. oh and for the "ebuild /var/db/pkg/net-dns/bind-9.2.3/bind-9.2.3.ebuild config" to work properly you have to edit one of the config files first (I think it does say that the default chroot path is /chroot which you might not want)
Well, recompiling does not work over here.
Recompiling changes the problem for me, now it doesn't say libdns but libisccfg.so.0 (Also a fresh install)
Ok, works over here too now. I emerged bind-9.2.2-r3 and upgraded it with bind-9.2.3, after that I re-emerged bind-tools and it worked. Nefreyu, please confirm or deconfirm this.
Works for me now, please notify me or a dev if it needs reopening.
No, this bug is not resolved. It is dependant on symptoms of several other bugs, namely the fact that bind and bind-tools share libs, and the bind-tools libs are now compiled as shared while the bind libs are compiled in their default behaviour - static. This bug only appears to resolve itself when the two packages are installed a) in the correct order, or b) one at a time per system. As to the original problem, I haven't been able to glom on to the reason for the library conflicts, nor has anyone from either the BIND or Gentoo community stepped forward to supply any opinions or positive answers as to why the nasty symlinks are required, and why the behaviour seems to vary on every system with a different configuration, including the most common behavioural difference - whether 9.2.3 is a fresh install or an upgrade. I'd sooner see this bug remain open for the next three years than see it labelled as "WORKSFORME" and forgotten about, even though it continues to persist. This is why BIND and BIND-TOOLS were marked -arch for all architectures. If anybody has any ideas on why this continues to be a problem (please, no "WORKS FOR ME" responses) I'm all open to suggestions.
Compiling from a stock bind-9.2.3.src builds and install fine with the following configure options: ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-threads --enable-ipv6=yes
tryed from a clean installed, gave me the same libdns.so.11 error as reported if I use the ebuild, but installed fine from sources with the command found on the previous post
Make some tests on my machine. Apparently the problem relies with the --with-libtool config option. It affect new (fresh installed) and upgraded systems. Without that option bind build without problem. Also made a change in the way bind-tools are managed. Instead of erasing them after install, just modify the Makefile to skip them since they are provided on another ebuild. I will include both diff from 9.2.3 current ebuild and the complete new ebuild. At last, bring some compile options from bind-tools in order to eliminate any discrepancy of code betweeen both. As a note, bug 32214 refer to the same problem (I think).
Created attachment 30571 [details] Changes done to bind-9.2.3.ebuild on portage
Created attachment 30572 [details] New ebuild with included changes In addition to the config option, I remove pkg_preinst() function with the lines that delete the binaries and docs of dig, host and nslookup and replaced with a sed hack that skips the bin/dig directory at build time, so no manual removal of those tools are needed on the ebuild anymore.
hopefuly fixed in 9.2.5. at least - unreproduceable reopen this bug, if it'll still occurs thanks everyone