Re: Can't compile Screen: Undefined reference to __imp__ospeed

Andrew Schulman writes: > I'm curious: where do you use this? Well, I'll admit to some degree that it's yak shaving (http://projects.csail.mit.edu/gsb/old-archive/gsb-archive/gsb2000-02-11.html), but the use case for me is running Screen locally and having multiple terminals open remotely, with

Re: Can't compile Screen: Undefined reference to __imp__ospeed

Andrew Schulman writes: > TERM=screen-256color screen > > gives 256 colors, at least in Cygwin 1.5. Can you confirm this? Yes. Beautiful, Andrew. You said you needed text for the release announcement. I'm not sure what it's supposed to look like, but you can use this, if it works: screen-

Re: Can't compile Screen: Undefined reference to __imp__ospeed

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 2

Re: Can't compile Screen: Undefined reference to __imp__ospeed

> I'm guessing that you need libncurses-devel. Yep. That's what I was missing. > If it compiles cleanly and is of > interest then I can certainly package a new release with it. Unfortunately, I can't get it to compile cleanly when I add --enable-colors256 to the cygconf line. The output from

Can't compile Screen: Undefined reference to __imp__ospeed

Hi, all. 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. I downloaded the package via the Cygwin installer and ran cygport screen-4.0.3-1.cygport almostall At compile, I get the followin