libncurses-devel-5.7-18 doesn't create /usr/include/curses.h

2010-08-14 Thread Ryan Johnson
Hi all, Getting compile errors about curses.h not found, and sure enough, it's not in /usr/include. After reinstalling libncurses-devel (I already had it), the problem didn't go away so I looked in the postinstall script. The comment at the top says: # This script will create symbolic

Re: libncurses-devel-5.7-18 doesn't create /usr/include/curses.h

2010-08-14 Thread Corinna Vinschen
On Aug 14 14:11, Ryan Johnson wrote: Hi all, Getting compile errors about curses.h not found, and sure enough, it's not in /usr/include. After reinstalling libncurses-devel (I already had it), the problem didn't go away so I looked in the postinstall script. The comment at the top says

1.5.25 cf. 1.7.1: an odd packaging finding for *curses.h

2010-01-19 Thread Fergus
... no --- checking for strcasestr... yes 86,91c86,91 checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking ncurses.h usability... yes checking ncurses.h presence... yes checking for ncurses.h... yes --- checking curses.h usability

1.5.25 cf. 1.7.1: an odd packaging finding for *curses.h

2010-01-19 Thread Charles Wilson
Fergus wrote: Is this a packaging error (nothing under /usr/include/) or, here only, has something gone strangely awry during setup? See: http://cygwin.com/ml/cygwin-announce/2010-01/msg2.html MAINTAINERS: You must now specify explicitly -I/usr/include/ncurses when compiling against

curses.h location in cygwin install?

2006-03-10 Thread Robin Lin
Hi everyone, I'm trying to use the curses library, and I can't seem to locate where the curses.h file is. I've tried to reinstall the curses packages several times, and I still can't locate the file. It's just not where everyone says it should be (\usr\include\ncurses). I don't even see

Re: curses.h location in cygwin install?

2006-03-10 Thread Bob Rossi
On Fri, Mar 10, 2006 at 08:38:57AM -0800, Robin Lin wrote: Hi everyone, I'm trying to use the curses library, and I can't seem to locate where the curses.h file is. I've tried to reinstall the curses packages several times, and I still can't locate the file. It's just not where everyone

Re: curses.h location in cygwin install?

2006-03-10 Thread Tony Richardson
Robin Lin rslin at ucdavis.edu writes: I'm trying to use the curses library, and I can't seem to locate where the curses.h file is. I've tried to reinstall the curses packages several times, and I still can't locate the file. It's just not where everyone says it should be (\usr\include

Re: curses.h (Attn: bash and setup maintainers)

2006-01-28 Thread Igor Peshansky
On Tue, 24 Jan 2006, Eric Blake wrote: According to Igor Peshansky on 1/23/2006 9:34 AM: Most of the messages are diagnostics to track script progress. The only exceptions are the lines below: ./00bash.sh.done: line 12: ./01bash.bat: No such file or directory cp: cannot stat

Re: curses.h (Attn: bash and setup maintainers)

2006-01-26 Thread Charles Wilson
Eric Blake wrote: Yes, but the devil is in the details. I'm trying to come up with some sort of generic solution where you add a file CYGWIN-PATCHES/upstream_patches.lst, whose contents (if the file exists) is a list of patch files that should be bundled into the patch tarball, and which should

Re: curses.h (Attn: bash and setup maintainers)

2006-01-25 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Peshansky on 1/24/2006 7:26 AM: Duly noted; bash-3.1-2 will improve on this situation (whenever I get time to get that working; I'm still struggling with gracefully incorporating upstream patches without wiping them out by rerunning

Re: curses.h (Attn: bash and setup maintainers)

2006-01-24 Thread Bob Rossi
In any case, looks like all the postinstall scripts ran for you, so you should be good to go. Hi Igor, So do you think that I broke CGDB somehow? When I compile and run it on Cygwin, it's display in the terminal is not correct. However, if I run a pre-compiled older version, it's display is

Re: curses.h (Attn: bash and setup maintainers)

2006-01-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Peshansky on 1/23/2006 9:34 AM: Most of the messages are diagnostics to track script progress. The only exceptions are the lines below: ./00bash.sh.done: line 12: ./01bash.bat: No such file or directory cp: cannot stat

Re: curses.h (Attn: bash and setup maintainers)

2006-01-24 Thread Igor Peshansky
On Tue, 24 Jan 2006, Eric Blake wrote: According to Igor Peshansky on 1/23/2006 9:34 AM: Most of the messages are diagnostics to track script progress. The only exceptions are the lines below: ./00bash.sh.done: line 12: ./01bash.bat: No such file or directory cp: cannot stat

Re: curses.h

2006-01-24 Thread Igor Peshansky
On Tue, 24 Jan 2006, Bob Rossi wrote: In any case, looks like all the postinstall scripts ran for you, so you should be good to go. Hi Igor, So do you think that I broke CGDB somehow? When I compile and run it on Cygwin, it's display in the terminal is not correct. However, if I run a

Re: curses.h

2006-01-23 Thread Bob Rossi
/curses.h is there, so CGDB goes through configure fine. I did try your suggestions about for I in *.sh.done; do ./$I; done, however, it was producing lot's of errors, so I stopped it. The problem is now, when I run CGDB, the terminal is being skewed. So the display is incorrect. However, if I run

Re: curses.h

2006-01-23 Thread Igor Peshansky
On Mon, 23 Jan 2006, Bob Rossi wrote: On Sat, Jan 21, 2006 at 05:31:24PM -0500, Igor Peshansky wrote: On Sat, 21 Jan 2006, Bob Rossi wrote: I will do this on Monday. However, is there a way to tell cygwin to fix all packages? Just in case others are broken? Once you have /bin/sh,

Re: curses.h

2006-01-23 Thread Bob Rossi
On Mon, Jan 23, 2006 at 11:06:09AM -0500, Igor Peshansky wrote: On Mon, 23 Jan 2006, Bob Rossi wrote: On Sat, Jan 21, 2006 at 05:31:24PM -0500, Igor Peshansky wrote: On Sat, 21 Jan 2006, Bob Rossi wrote: I will do this on Monday. However, is there a way to tell cygwin to fix all

Re: curses.h (Attn: bash and setup maintainers)

2006-01-23 Thread Igor Peshansky
On Mon, 23 Jan 2006, Bob Rossi wrote: On Mon, Jan 23, 2006 at 11:06:09AM -0500, Igor Peshansky wrote: On Mon, 23 Jan 2006, Bob Rossi wrote: On Sat, Jan 21, 2006 at 05:31:24PM -0500, Igor Peshansky wrote: On Sat, 21 Jan 2006, Bob Rossi wrote: I will do this on Monday. However,

Re: curses.h

2006-01-21 Thread Eric Blake
that would cause this? Let's look at this a little closer: configure:6066: checking curses.h presence configure:6076: gcc -E conftest.c conftest.c:49:20: curses.h: No such file or directory configure:6082: $? = 1 Somehow, you've messed up your compilation environment. You need to figure

Re: curses.h

2006-01-21 Thread Bob Rossi
changed with Cygwin that would cause this? Let's look at this a little closer: configure:6066: checking curses.h presence configure:6076: gcc -E conftest.c conftest.c:49:20: curses.h: No such file or directory configure:6082: $? = 1 Somehow, you've messed up your compilation

Re: curses.h

2006-01-21 Thread Brian Dessent
Bob Rossi wrote: [EMAIL PROTECTED] ~/cvs/cgdb/builddir/tmp] $ cat foo.c #include curses.h [EMAIL PROTECTED] ~/cvs/cgdb/builddir/tmp] $ gcc -c foo.c foo.c:1:20: curses.h: No such file or directory The ncurses headers live in /usr/include/ncurses. Normally this means that you need

Re: curses.h

2006-01-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Rossi on 1/21/2006 8:15 AM: Yup, things are screwed up all right. Not Found: sh Use setup.exe to reinstall the bash package; I would also reinstall libncurses-devel in case its postinstall failed to run because of problems with

Re: curses.h

2006-01-21 Thread Bob Rossi
On Sat, Jan 21, 2006 at 11:33:42AM -0700, Eric Blake wrote: According to Bob Rossi on 1/21/2006 8:15 AM: Yup, things are screwed up all right. Not Found: sh Use setup.exe to reinstall the bash package; I would also reinstall libncurses-devel in case its postinstall failed to run

Re: curses.h

2006-01-21 Thread Igor Peshansky
On Sat, 21 Jan 2006, Bob Rossi wrote: On Sat, Jan 21, 2006 at 11:33:42AM -0700, Eric Blake wrote: According to Bob Rossi on 1/21/2006 8:15 AM: Yup, things are screwed up all right. Not Found: sh Use setup.exe to reinstall the bash package; I would also reinstall

curses.h

2006-01-20 Thread Bob Rossi
Hi all, This is yet another problem that I am having, that did not used to exist. My configure script checks for curses.h and ncurses.h, since I depend on curses to compile CGDB. This used to be detected, but no longer does. checking ncurses.h usability... no checking ncurses.h presence

Re: curses.h

2006-01-20 Thread Igor Peshansky
On Fri, 20 Jan 2006, Bob Rossi wrote: This is yet another problem that I am having, that did not used to exist. My configure script checks for curses.h and ncurses.h, since I depend on curses to compile CGDB. This used to be detected, but no longer does. checking ncurses.h usability

Has a solution been found to the problem with curses.h-termcap.h-tparm?

2005-03-07 Thread Eric Lilja
to build MySQL (either of the above mentioned versions), both compilations end with an error described here (I found this using google): http://www.cygwin.com/ml/cygwin/2004-12/msg00392.html Seems like the MySQL source is including both termcap.h and curses.h, which brings to conflicting tparm types

curses.h / termcap.h: conflicting types of tparm (was: Re: Error Compiling Mysql 4.1.7)

2004-12-12 Thread Gerrit P. Haase
Got it now after retrying. IIRC this was already reported, I report this again now with the according subject (only cygwin list for now): curses.h / termcap.h: conflicting types of tparm This error happens when compiling the MySQL client v4.1.7 term.c because both headers are included

Re: curses.h / termcap.h: conflicting types of tparm

2004-12-12 Thread Charles Wilson
Gerrit P. Haase wrote: curses.h / termcap.h: conflicting types of tparm This error happens when compiling the MySQL client v4.1.7 term.c because both headers are included. There are two locations to report this, the cygwin main list and the mysql list, because it may be unusual to include both