[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: pkg/46639: irssi port disables ncurses on non-NetBSD platforms
The following reply was made to PR pkg/46639; it has been noted by GNATS.
From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
Subject: Re: pkg/46639: irssi port disables ncurses on non-NetBSD platforms
Date: Fri, 6 Jul 2012 13:56:19 -0400
On Fri, 6 Jul 2012 04:50:04 +0000 (UTC)
Matthew Mondor <mm_lists%pulsar-zone.net@localhost> wrote:
> I've seen no apparent difference at first, but I noticed that despite
> LANG set to en_US.UTF-8, if built with ncurses support on NetBSD,
> pasting some UTF-8 into a channel causes it to be displayed incorrectly
> (I'm not sure if it happens because of input or output translation or
> both), while this works fine for terminfo builds.
> Moritz, would it be possible to test this version in your environment,
> to confirm that it builds with ncurses and works fine? A shell archive
> of the already patched irssi pkgsrc stub is also attached for
I tested it successfully on an Ubuntu 12.04 system with ncurses.
Unfortunately, UTF-8 encoding with unicode characters still seems
problematic. I wonder if it's not because ncurses was selected
rather than ncursesw, or if we build pkgsrc ncurses with wrong config
If I try to build it with terminfo on Linux, I however get a
"configure: error: Terminfo/termcap not found - install ncurses-devel
package" error, despite both Ubuntu ncurses-dev and pkgsrc ncurses
having been installed. I don't think this matters much though, as those
systems already have ncurses, and it's the option selected by default
on non-NetBSD systems.
An interesting thing is that pkgsrc vim did build successfully against
the native Ubuntu libtinfo (it also includes the termcap buildlink
file), and that unicode works fine with it, with utf-8 encoding. So I
suspect the configure script of irssi might need some patch to properly
detect the presence of libtinfo and use it.
Main Index |
Thread Index |