[
https://issues.apache.org/jira/browse/TS-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478845#comment-15478845
]
Susan Hinrichs commented on TS-4152:
------------------------------------
I had problems building on rhel6 after pulling in this change. traffic_cop
wouldn't build because it didn't believe that I had ncursesw. Once I reverted
this commit all was fine. I see that it built on jenkins, so I assume there
are some other intermediate files I need to kill beyond the autoreconf and
rerunning configure? Once I get done with my current branch, I'll create a new
git clone and that hopefully clears things up.
> Build failure when curses is not available
> ------------------------------------------
>
> Key: TS-4152
> URL: https://issues.apache.org/jira/browse/TS-4152
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Reporter: James Peach
> Assignee: Jason Kenny
> Labels: newbie
> Fix For: 7.0.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> On Centos6 w/ devtoolset-3:
> {code}
> checking for NcursesW wide-character library... yes
> checking for working ncursesw/curses.h... no
> checking for working ncursesw.h... no
> checking for working ncurses.h... no
> configure: WARNING: could not find a working ncursesw/curses.h, ncursesw.h or
> ncurses.h
> ...
> Making all in traffic_top
> make[2]: Entering directory
> `/home/vagrant/trafficserver-6.1.0/cmd/traffic_top'
> CXX traffic_top.o
> traffic_top.cc:51:2: error: #error "SysV or X/Open-compatible Curses header
> file required"
> #error "SysV or X/Open-compatible Curses header file required"
> {code}
> The build is not supposed to try to build {{traffic_top}} if ncurses is not
> available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
