[MacPorts] #29334: fizmo 0.6.9 update
MacPorts
noreply at macports.org
Sun May 1 23:05:47 PDT 2011
#29334: fizmo 0.6.9 update
----------------------------------------------+-----------------------------
Reporter: Christoph.Ender@… | Owner: macports-tickets@…
Type: update | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: haspatch | Port: fizmo
----------------------------------------------+-----------------------------
Comment(by Christoph.Ender@…):
Replying to [comment:3 ryandesign@…]:
> Thanks for the new diff.
> Replying to [comment:2 Christoph.Ender@…]:
> > > Your new port removes the ncursesw and libxml2 dependencies that
were there.
> > This is an intentional change […]
> I'm not sure what you mean by "Mac OS X is not a supported platform for
ncurses".
Sorry, that wasn't very precise. Before asking for support on the ncurses
bug list, I found out that http://invisible-
island.net/ncurses/ncurses.faq.html states “And a few other platforms such
as Mac OS X have been reported to work”, Mac OS X is neither listed in the
“known to work”, nor in the “8-bit-charachters are known to work” section.
So, this should have been that Mac OS X probably hasn't been tested
officially.
> Obviously ncurses works on Mac OS X, since both Mac OS X and MacPorts
include it, and tons of other ports use MacPorts ncurses without issue.
I did not say it does not work. I just found out that displaying a non-
ASCII char using the “echo_wchar” function will cause errno != 0 to be
set. I've attached a tiny code snippet that should illustrate the problem.
I've tested this on Mac OS X and Linux (the only other unix platform
that's currently available to me), and for ncurses 5.9, errno is != 0 on
Mac OS X, 0 on linux. Replies on the ncurses-bug mailing list have been
inconclusive, leaving me to the choice whether to set errno=0 after every
echo_wchar() or refresh() function call, or alternatively to include the
Mac OS X version for the time being. I'm aware that this isn't a good
solution, I'm open to suggestions how to resolve this in some other way.
--
Ticket URL: <https://trac.macports.org/ticket/29334#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list