Error: "curses not found" when trying to ./configure tmux for iterm2

9,900 views
Skip to first unread message

Michael Garrett

unread,
Mar 30, 2013, 6:46:37 AM3/30/13
to iterm2-...@googlegroups.com
I'm having trouble compiling tmux for iTerm.  I keep getting  this error:

configure: error: "curses not found"

when running the ./configure step of tmux.

Here is what I did:

* downloaded tmux-for-iTerm2-20130319.tar.gz and extracted it
* downloaded tmux-deps-v2.tar.gz and extracted it and all of the tar.gz files in it
* compiled each of the deps individually using these 3 commands:

 1008  ./configure --disable-shared --prefix=/u/mgarrett/tmux2
 1009  make clean
 1010  make
 1011  make install

Intentionally installing them in a local directory that I have access to.  (don't have write access on this machine)

Then I run this command in the tmux directory:

./configure --prefix=/u/mgarrett,spin/tmux CFLAGS="-I/u/mgarrett,spin/tmux2/include" LDFLAGS="-L/u/mgarrett,spin/tmux2/lib"

After lots of churning it results in this error:

configure: error: "curses not found"

I first tried to get around the error by "yum install" on every ncurses thing that I could find.  (most of which were already there)  That resulted in the same error.

Next I went to the ncurses sourceforge page, downloaded  their package, and compiled it using the same 4 commands that I used above for all of the deps.  Same error when i went to run ./configure on tmux.

I then reread the tmux page and noticed that the main page says "needs libevent and ncurses".  So I downloaded it from their link (different than the ncurses download page that I used before) and ran the same 4 commands that I did for the other deps at the top of this post.  That seemed to complete, but it didn't change  the error that I am getting when I run ./configure on tmux.  It still says: 

configure: error: "curses not found"

Of note, it does say higher up in the output these ncurses related things:

checking ncurses.h usability... yes
checking ncurses.h presence... yes
checking for ncurses.h... yes

What am I doing wrong?  Is there a curses package that I need that isn't "n"curses?  Or are my compile steps wrong?  

I am regrettably a hack at compiling c code, so I'm sorry if this is a really ignorant question.

-Mike

Chas. Owens

unread,
Apr 4, 2013, 7:23:20 AM4/4/13
to iterm2-...@googlegroups.com
Have you tried

yum install ncurses-devel

To compile you need the devel packages.


--
You received this message because you are subscribed to the Google Groups "iterm2-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iterm2-discus...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Chas. Owens
wonkden.net
The most important skill a programmer can have is the ability to read.

Michael Garrett

unread,
Apr 4, 2013, 9:30:35 AM4/4/13
to iterm2-...@googlegroups.com
Yes, I do have the ncurses-devel package installed, and I installed it as one of the steps to try to fix this problem.


[mgarrett@rh6-pbc2b6-06 tmux] ./configure --prefix=/u/mgarrett,spin/tmux CFLAGS="-I/u/mgarrett,spin/tmux2/include" LDFLAGS="-L/u/mgarrett,spin/tmux2/lib"
checking for a BSD-compatible install... /usr/software/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/software/bin/mkdir -p

<cutting a bunch of output to make this readable>

checking pkg-config is at least version 0.9.0... yes
checking for LIBEVENT... yes
checking for library containing setupterm... no
configure: error: "curses not found"

[mgarrett@rh6-pbc2b6-06 tmux] rpm -qa | grep curses
ncurses-libs-5.7-3.20090208.el6.x86_64
ncurses-devel-5.7-3.20090208.el6.x86_64  <---Here it is
ncurses-5.7-3.20090208.el6.x86_64
ncurses-base-5.7-3.20090208.el6.x86_64

-Mike

Rick Hornsby

unread,
Apr 5, 2013, 11:17:13 AM4/5/13
to iterm2-...@googlegroups.com



On Sat, Mar 30, 2013 at 5:46 AM, Michael Garrett <mg.no...@gmail.com> wrote:
-snip-

I am regrettably a hack at compiling c code, so I'm sorry if this is a really ignorant question.

OT, but just to encourage you a bit - compiling is a bit of an arcane art, and when it goes wrong, it can be very difficult to figure out.  Questions are good.  They're one way we learn.  From your email, it seems like you were being very thorough and tried to solve the problem on your own.  Most of us on this list probably have *nix backgrounds, and we all had to start somewhere.  Maybe I'm a little old school, but I remember the guys who taught me and answered my questions.  Most *nix guys I know are good like that.



David Miller

unread,
Mar 7, 2014, 6:09:21 PM3/7/14
to iterm2-...@googlegroups.com
Michael Garrett wrote:
> checking pkg-config is at least version 0.9.0... yes
> checking for LIBEVENT... yes
> checking for library containing setupterm... no
> configure: error: "curses not found"
>
> [mgarrett@rh6-pbc2b6-06 tmux] rpm -qa | grep curses
> ncurses-libs-5.7-3.20090208.el6.x86_64
> ncurses-devel-5.7-3.20090208.el6.x86_64 <---Here it is
> ncurses-5.7-3.20090208.el6.x86_64
> ncurses-base-5.7-3.20090208.el6.x86_64
Forgive me for resurrecting such an old thread, but since there was
never an answer posted here and Google points at this thread when
researching this error I figured I'd followup and provide the answer I
found in case it helps anyone else in the future.

The fix was to install the "glibc-static" package.

It attempts to statically link ncurses, and ncurses has a dependency on
glibc. So in order to statically link ncurses you also have to
statically link glibc, which requires the static versions of the glibc
libraries, which RHEL and CentOS don't include by default.

Alma Tz.

unread,
Feb 13, 2015, 2:13:57 PM2/13/15
to iterm2-...@googlegroups.com
Hi all,

Dave, (even if late)
Thank you for responding to this topic...very useful..
I was going through the code to understand the WHY..
Cheers

Michael Garrett

unread,
Feb 17, 2015, 11:28:21 AM2/17/15
to iterm2-...@googlegroups.com
After updating to the recent nightly build, I am seeing a problem where my command prompt is below the bottom of the screen after output causes scrolling.

In other words, if I:

1.  open a new window
2.  dump something to the screen that is a few lines longer than the window is tall.  My default size is 24 rows tall, so , if I do this to print 25 numbered lines ( perl -e 'for (1..25) { print "$_\n"; }'  ) , I won’t see my cursor.  It is off of the bottom of the screen.  Here is a screen capture of my missing cursor line after running that exact command.


And, the prompt line remains off of the screen.  I can hit enter and type stuff endlessly, but until I exceed a few lines of text to cause a single command to scroll, I don’t get to see what I have typed.

I tried number of settings changes to see if I could identify a setting that plays a part in this effect.  Things like font type and size played no part in it.  I tried a bunch of other things, including creating a new profile with no customized settings, and it also has the problem that I described.  The one setting that fixes this for me is under the Window tab, style=No Title Bar.  Here is a screen capture showing that my 25 line generator works and lets me see the command prompt when it has scrolled.


Just in case it matters, I am seeing this problem on a mid 2013 Retina Macbook Pro.  

-Mike

George Nachman

unread,
Feb 21, 2015, 4:46:23 PM2/21/15
to iterm2-...@googlegroups.com
Hi Michael,
Sorry for the delay--I'm on parental leave right now and I don't have as much time as normal.

This is a serious problem--can you please send me your ~/Library/Preferences/com.googlecode.iterm2.plist file? Either reply to me or file an issue.

It looks like something is messed up with the tab bar. I hope I can reproduce it with your config.

Thanks,
George

--
You received this message because you are subscribed to the Google Groups "iterm2-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iterm2-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Michael Garrett

unread,
Feb 23, 2015, 9:27:17 AM2/23/15
to iterm2-...@googlegroups.com
George,

 If “parental leave” means what I think it does, congrats!

 I’ve attached my plist file to this email.  Disclaimer, I reverted back to Build 2.9.20150206-nightly last week because the effects I described were pretty tough for me to work with.  (I never found a way to move a window that had no title bar, which was my workaround).  I mention the revert just in case it changes the plist file.  If it does, just tell me and I will go back to the later nightly to get you an effected plist file.

com.googlecode.iterm2.plist

Michael Garrett

unread,
Mar 17, 2015, 10:15:06 AM3/17/15
to iterm2-...@googlegroups.com
I am running Build 2.9.20150302-nightly, but I think this behavior has been wrong or broken for a couple of months now.

In Preferences | General | Characters considered part of word for selection,,, I have this: /-+\~_.:?=&,

So, double clicking on any part of this string should highlight the whole string:

smkfiler.mgmt.smoke:/share/system/bubble

But, it doesn’t. If I double click anywhere before the : only smkfiler.mgmt.smoke is highlighted. Anywhere after the : and only /share/system/bubble is highlighted. If I double click right on the : the whole string is highlighted the way it should be.

The same problem happens with this string:

/u/mgarrett,spin/p4/smoke/scripts

The comma acts exactly like the colon does above.


-Mike
ps. thanks for your work on iterm. I love it.


George Nachman

unread,
Mar 18, 2015, 6:12:45 PM3/18/15
to iterm2-...@googlegroups.com
I suspect that you have "prefs>pointer>double-click performs smart selection" turned on. Clearly, these two settings need to be right next to each other and turning on DCPSS should disable CCPOWFS. I'll file an issue for that.

If I am wrong, please file an issue and include the plist file as requested in the bug template. Thanks!

Michael Garrett

unread,
Mar 25, 2015, 4:10:54 PM3/25/15
to iterm2-...@googlegroups.com
You were correct, I had smart selection turned on.  Turning that off made double click act as I expected it to.  Thanks.
Reply all
Reply to author
Forward
0 new messages