On Thu, Jan 03, 2013 at 08:13:39AM +0000, Christian Ebert wrote:
* Michael Elkins on Thursday, January 03, 2013 at 01:14:16 +0000
Good catch. I just commmited a patch that will print
+/-NCURSES_WIDECHAR next to the ncurses version to make it clear which
lib mutt is compiled against.
Not sure whether it gives reliable diagnostics everywhere:
$ uname -mprsv
Darwin 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009;
root:xnu-1228.15.4~1/RELEASE_I386 i386 i386
$ mutt -v | fgrep -i curses
ncurses: ncurses 5.9.20121229 (compiled with 5.9) -NCURSES_WIDECHAR
Configure options: '--prefix=/usr/local' '--disable-nls' '--enable-hcache'
'--with-idn=/sw' '--with-homespool=Maildir' '--with-curses=/usr/local'
'--with-libiconv-prefix=/sw'
$ otool -L `which mutt`
/usr/local/bin/mutt:
/usr/local/lib/libncursesw.5.dylib (compatibility version 5.0.0,
current version 5.0.0)
/usr/local/lib/libtokyocabinet.9.dylib (compatibility version 9.0.0,
current version 9.11.0)
/sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version
7.0.0)
/sw/lib/libidn.11.dylib (compatibility version 18.0.0, current version
18.5.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version
1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.1.7)
Shouldn't that yield +NCURSES_WIDECHAR?
Yes, it should. I guess this the same problem I was trying to
solve in 6241:36b0cc717ecc that didn't work under OSX:
#if defined(_XOPEN_SOURCE_EXTENDED) || defined(_XPG5)
#define NCURSES_WIDECHAR
#endif
I've backed out my patch for the time being.
