X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Andrew Schulman Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed Date: Thu, 29 Jan 2009 10:53:26 -0500 Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Note-from-DJ: This may be spam > I'm using a Perl script, available at > http://www.frexx.de/xterm-256-notes/data/256colors2.pl, to test whether my > terminal is giving me 256 colors. Thanks, this is helpful. > It works when I run it from a vanilla bash > prompt, but not from within Screen, even after I installed your build. OK. Same here. I get a variety of different results with different combinations of Cygwin version (1.5, 1.7), terminal type (DOS, xterm) and with/without screen. Without modification, the only combination that gives 256 colors for me is Cygwin 1.5, xterm, without screen. All others give 8 colors, and the colormap is garbled in the DOS terminals (big surprise). However, in /usr/share/terminfo/s, there is a variety of screen* files, including several named screen-256color*. So it turns out that for me, running TERM=screen-256color screen gives 256 colors, at least in Cygwin 1.5. Can you confirm this? In Cygwin 1.7, I still only get 8 colors. I'll report that separately as a bug. Andrew. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/