510930 – dev-util/cmake-2.8.12.2::gentoo: failed to compile, undefined reference to symbol 'cbreak'

Bug 510930 - dev-util/cmake-2.8.12.2::gentoo: failed to compile, undefined reference to symbol 'cbreak'

Summary: dev-util/cmake-2.8.12.2::gentoo: failed to compile, undefined reference to sy...

Status:	RESOLVED DUPLICATE of bug 468622

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Development (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo KDE team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-05-21 12:11 UTC by rochus
Modified:	2014-05-21 12:20 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
emerge --info '=dev-util/cmake-2.8.12.2::gentoo' (infobar,18.16 KB, text/plain) 2014-05-21 12:11 UTC, rochus	Details
emerge build log for cmake-2.8.12.2 (build.log,364.42 KB, text/x-log) 2014-05-21 12:12 UTC, rochus	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description rochus 2014-05-21 12:11:05 UTC

When trying to compile cmake-2.8.12.2 (currently marked as stable), the compilation fails with the message "undefined reference to symbol 'cbreak'". I assume this comes from ncurses being built with the tinfo USE flag here. That use flag is required for nvidia-cuda, though.

Reproducible: Always

Steps to Reproduce:
1. MAKEFLAGS=-j1 sudo emerge --update --oneshot cmake
Actual Results:  
compilation fails.

Expected Results:  
build + install.

Comment 1 rochus 2014-05-21 12:11:48 UTC

Created attachment 377370 [details]
emerge --info '=dev-util/cmake-2.8.12.2::gentoo'

Comment 2 rochus 2014-05-21 12:12:44 UTC

Created attachment 377372 [details]
emerge build log for cmake-2.8.12.2

Comment 3 Johannes Huber (RETIRED) gentoo-dev

2014-05-21 12:18:18 UTC


*** This bug has been marked as a duplicate of bug 468622 ***

Comment 4 rochus 2014-05-21 12:20:02 UTC

Thanks! I did not spot that Bug 468622 was the same.