[Bug 204770] converters/libiconv r398996 patch breaks libidn

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Nov 24 00:13:28 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204770

--- Comment #2 from wxl at bikefriday.com ---
Specifically, mutt complains about a non-intentional hostname not being
properly internationalized:
Bad IDN in "from": 'jeeves.bf-internal.com'

Re-compiling without IDN support solves the problem. Thus, the problem lies in
libidn. However, since the last successful run, libidn had not changed, so it's
a dependency of libidn that's changed. The only one that I could find that has
changed is libiconv. 

I recognize this may be a logical error, but I'm inclined to believe that
reporting an error can, at worst, lead to refiling a report where it properly
belongs. However, nothing gets changed if it doesn't get reported at all.

So here's what I do know:

mutt's compose.c includes this aforementioned error:
http://dev.mutt.org/hg/mutt/file/e635ce43b001/compose.c#l609
which calls on mutt_idna.c:
hhttp://dev.mutt.org/hg/mutt/file/e635ce43b001/mutt_idna.c
the heavy lifting there is using idna_to_unicode_8z8z() and idna_to_ascii_8z().

And that's about where I get lost. libidn confusingly says iconv isn't strictly
required:
http://git.savannah.gnu.org/gitweb/?p=libidn.git;a=blob;f=configure.ac;h=dc340dab04082e23e364f0edbffcd90a4920e00f;hb=b45deaf855dfec2bb1d13f5bf306829e62f35ade#l59
and yet it is.

So I'm hoping someone with a little more intimiacy might be able to help more.
Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-gnome mailing list