can't use underscores(_) when emerge net-dns/bind-tools with --enable-runidn. Reproducible: Always Steps to Reproduce: 1.compile net-dns/bind-tools with '--enable-runidn --with-idn' 2.can't work next command with error messages. # dig default._domainkey.example.jp TXT convert UTF-8 textname to IDN encoding: prohibited character found 3.if compile it without '--enable-runidn --with-idn' it works. I think, idnkit have to change '_' checking.
*** Bug 218688 has been marked as a duplicate of this bug. ***
*** Bug 218694 has been marked as a duplicate of this bug. ***
I wasn't able to reproduce this with neither 9.4.1_p1 nor 9.4.2. Plus i couldn't find "--enable-runidn --with-idn" in bind or bind-tools.
I can find '--enable-runidn --with-idn' # cd ....../bind-9.4.x # ./configure --help and I set in /etc/portage/bashrc as follows; if [ "${CATEGORY}/${PN}" = "net-dns/bind" ] ; then EXTRA_ECONF='--enable-runidn --with-idn' fi if [ "${CATEGORY}/${PN}" = "net-dns/bind-tools" ] ; then EXTRA_ECONF='--enable-runidn --with-idn' fi
Sorry > I can find '--enable-runidn --with-idn' > # cd ....../bind-9.4.x > # ./configure --help is not true. I set USE=... idn ..." and /etc/portage/bashrc if [ "${CATEGORY}/${PN}" = "net-dns/bind" ] ; then EXTRA_ECONF='--enable-runidn --with-idn' fi if [ "${CATEGORY}/${PN}" = "net-dns/bind-tools" ] ; then EXTRA_ECONF='--enable-runidn --with-idn' fi configure of net-dns/bind-tools-9.4.1_p1 is ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-ipv6 --build=i686-pc-linux-gnu --enable-runidn --with-idn w/o '--enable-runidn --with-idn', domain name 'japanese KANJI' can't be used. with --enable-runidn --with-idn', '_' can't be used.
(In reply to comment #4) > and I set in /etc/portage/bashrc as follows; > if [ "${CATEGORY}/${PN}" = "net-dns/bind" ] ; then > EXTRA_ECONF='--enable-runidn --with-idn' > fi > if [ "${CATEGORY}/${PN}" = "net-dns/bind-tools" ] ; then > EXTRA_ECONF='--enable-runidn --with-idn' > fi > You can probably imagine that we can't support your personal hacks ... Anyways, though bind-tools had an idn use-flag it didn't link to libidnkit until now. I fixed that in bind-tools-9.4.2 (CVS rev 1.2), please sync your portage tree and test with 9.4.2 (note the CVS rev mentioned). Please check if dig for example is linked against libidnkit. For the "--enable-runidn" you mentioned, from my understanding this would build an additional runidn binary which would make non-idn-aware applications idn-aware on the fly. As we link libidnkit this isn't needed.
(In reply to comment #6) > ... I fixed that in bind-tools-9.4.2 (CVS rev 1.2) ... CVS rev 1.3 that is ...
(In reply to comment #6) > > You can probably imagine that we can't support your personal hacks ... > I don't think so, The KANJI is being used by half of the world. The 'KANJI' is more than 15000 characters, idnkit is something to use a kanji by dns service. Then it's hacks for half of the world.
(In reply to comment #8) > > You can probably imagine that we can't support your personal hacks ... > > > > I don't think so, The KANJI is being used by half of the world. The 'KANJI' is > more than 15000 characters, idnkit is something to use a kanji by dns service. > Then it's hacks for half of the world. > There's a difference between hacking up /etc/portage/bashrc (and that's for sure a thing we can't and won't support) and a bug in bind-tools (dig etc.) not being linked to libidnkit (which this bug seems to be *really* about) when the idn use is set.