This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Fri, 23 Aug 2013 19:53:21 +0200
- Subject: Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
- References: <52162CA9 dot 9080002 at etr-usa dot com> <20130822171419 dot GQ2562 at calimero dot vinschen dot de> <CA+sc5mnedD0hOfzwTWYzy0QVhKC9gg-C68Nxfska-HG0HFOpLQ at mail dot gmail dot com> <20130823094919 dot GT2562 at calimero dot vinschen dot de> <52178ED2 dot 4090806 at etr-usa dot com>
Warren Young writes:
> Line 30 of main.ml is:
>
> assert (cbreak ());
>
> So....ncurses isn't working correctly across the exec() boundary?
I don't think ncurses can work without a tty interface and that's one of
the things you've lost through the "foreign" exec. You'd need something
like starting a 32bit mintty or rxvt-native to run orpie in, I suppose.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple