From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed
Date: Mon, 26 Jan 2009 22:33:00 -0000 [thread overview]
Message-ID: <u3asn41ivnl7ml3vg5nubdh756dh7te9lg@4ax.com> (raw)
In-Reply-To: <loom.20090126T051539-969@post.gmane.org>
Hi Justin.
> I'm trying to compile GNU Screen under Cygwin. Right now, I'm failing to
> compile an unmodified package, but my goal is to compile with 256 color support.
Hm, I hadn't looked at that option before. If it compiles cleanly and is of
interest then I can certainly package a new release with it.
> display.o:display.c:(.text+0x76d): undefined reference to `__imp__ospeed'
I don't have this problem when I compile screen. ospeed is defined in
termcap.h, which comes in termcap and libncurses-devel. I'm guessing that you
need libncurses-devel.
Let us know if that works and if the 256-color support works.
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/
next prev parent reply other threads:[~2009-01-26 21:23 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 [this message]
2009-01-27 3:19 ` Justin L.
2009-01-28 2:08 ` Andrew Schulman
2009-01-28 10:19 ` Justin L.
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=u3asn41ivnl7ml3vg5nubdh756dh7te9lg@4ax.com \
--to=schulman.andrew@epamail.epa.gov \
--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).