/var/tmp/portage/net-analyzer/icinga2-2.7.0-r1/work/icinga2-2.7.0/test/icinga-checkresult.cpp: In function ‘void icinga_checkresult::NotificationHandler(const Ptr&, icinga::NotificationType)’: /var/tmp/portage/net-analyzer/icinga2-2.7.0-r1/work/icinga2-2.7.0/test/icinga-checkresult.cpp:44:2: error: ‘cout’ is not a member of ‘std’ std::cout << "Notification triggered: " << Notification::NotificationTypeToString(type) << std::endl; ^~~ /var/tmp/portage/net-analyzer/icinga2-2.7.0-r1/work/icinga2-2.7.0/test/icinga-checkresult.cpp: In member function ‘void icinga_checkresult::host_1attempt::test_method()’: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170903-225953 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) [3] pypy (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv net-analyzer/icinga2 [ebuild N ] net-analyzer/icinga2-2.7.0-r1 USE="mysql plugins vim-syntax -apache2 -classicui -console -libressl -lto -mail -minimal -nano-syntax -postgres -studio"
Created attachment 494986 [details] emerge-info.txt
Created attachment 494988 [details] emerge-history.txt
Created attachment 494990 [details] environment
Created attachment 494992 [details] etc.portage.tbz2
Created attachment 494994 [details] logs.tbz2
Created attachment 494996 [details] net-analyzer:icinga2-2.7.0-r1:20170916-063745.log
Created attachment 494998 [details] temp.tbz2
I suspect this is a gcc issue, but I can't help but wonder how cout is not a part of the c++ standard library (my ancient c++ knowledge used cout a bit back in high school).
icinga-checkresult.cpp is simply missing a > #include <iostream> Icinga Github-Issue: https://github.com/Icinga/icinga2/issues/5613
fixed in 2.7.1 in place (build issue)
This isn't fixed. The same problem affects other files. I've added pertinent information on the upstream bug report.