From: Justin L. <starwiz@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed
Date: Wed, 28 Jan 2009 10:19:00 -0000 [thread overview]
Message-ID: <loom.20090128T064317-555@post.gmane.org> (raw)
In-Reply-To: <losun4dma3qh4eiflilod15lgr64c5ait4@4ax.com>
Thanks for looking at this, Andrew.
I might have messed something up, but after extracting your build, I still don't
get 256 colors within a Screen terminal.
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. It works when I run it from a vanilla bash
prompt, but not from within Screen, even after I installed your build.
Just to prove to myself that I actually did extract your (Cygwin 1.5) screen.exe
properly, I checked the hash:
e240a3ddc95d6ccaf08cfaa00fe3ab02 */usr/bin/screen.exe
whereas the screen.exe I got online has the following hash:
005bde6eb8eca29f1fdf73efbd5a83a5 */screen.exe
So...they are different. Maybe something *else* is wrong with my configuration.
Thanks again for your help, Andrew.
-Justin
--
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/
next prev parent reply other threads:[~2009-01-28 6:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 9:57 Justin L.
2009-01-26 22:33 ` Andrew Schulman
2009-01-27 3:19 ` Justin L.
2009-01-28 2:08 ` Andrew Schulman
2009-01-28 10:19 ` Justin L. [this message]
2009-01-29 17:07 ` Andrew Schulman
2009-01-29 20:28 ` Justin L.
2009-01-29 22:54 ` Andrew Schulman
2009-01-30 9:34 ` Justin L.
2009-01-30 13:02 ` Andrew Schulman
2009-02-19 16:09 ` Presto Ten
2009-02-19 16:27 ` Andrew Schulman
2009-02-19 17:55 ` Matt Wozniski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20090128T064317-555@post.gmane.org \
--to=starwiz@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).