public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: Can't compile Screen: Undefined reference to __imp__ospeed
Date: Wed, 28 Jan 2009 02:08:00 -0000	[thread overview]
Message-ID: <losun4dma3qh4eiflilod15lgr64c5ait4@4ax.com> (raw)
In-Reply-To: <loom.20090126T233225-348@post.gmane.org>

> >>> Installing screen-4.0.3-1
> /usr/src/screen-4.0.3-1/src/screen-4.0.3/etc/mkinstalldirs
> /usr/src/screen-4.0.3-1/inst/usr/bin /usr/src/screen-4.0.3-1/inst`sed < config.h
> -n -e '/define SCREENENCODINGS/s/^.*"\([^"]*\)"/\1/p'`
> /usr/bin/install -c screen /usr/src/screen-4.0.3-1/inst/usr/bin/screen
> /usr/bin/install: cannot create regular file
> `/usr/src/screen-4.0.3-1/inst/usr/bin/screen.exe': No such file or directory

I'm not sure why this step fails.  It seems that either screen.exe or its
installation directory, /usr/src/screen-4.0.3-1/inst/usr/bin, haven't been
created as they should have been.

I just ran this without any trouble, with --enable-colors256.  However, I'm not
quite sure how to test that option.  Can you please give my packages a try?  If
they work for you, and especially the 256-color support, let me know and I'll
release them to the repository.

# for Cygwin 1.5:
 http://home.comcast.net/~andrex2/cygwin-1.5/screen/screen-4.0.3-3.tar.bz2
 http://home.comcast.net/~andrex2/cygwin-1.5/screen/screen-4.0.3-3-src.tar.bz2

# for Cygwin 1.7:
 http://home.comcast.net/~andrex2/cygwin-1.7/screen/screen-4.0.3-4.tar.bz2
 http://home.comcast.net/~andrex2/cygwin-1.7/screen/screen-4.0.3-4-src.tar.bz2

Once you've downloaded the binary package, kill all of your screen sessions, run
e.g.

  tar -C/ -xf screen-4.0.3-3.tar.bz2

and then restart screen as usual to test.

It would also be helpful if you would give a brief description for the release
announcement, of what that option does and how to use it.

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/

  reply	other threads:[~2009-01-27 21:07 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 [this message]
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=losun4dma3qh4eiflilod15lgr64c5ait4@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).