Good question, and you could remove the line and build and see what happens. Also, you could read the upstream build instructions and configure.ac or equivalent and see if curses is documented as a dependency. It may be that we could instead patch out some incorrect attempt to use curses.