Your message dated Thu, 10 Apr 2025 03:59:03 +0300 with message-id <Z/cX14JJt3be6Fcn@localhost> and subject line Fixed since 0.13.0-2 has caused the Debian Bug report #1075103, regarding jnettop: ftbfs with GCC-14 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1075103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075103 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:jnettop Version: 0.13.0-1.2 Severity: important Tags: sid trixie User: [email protected] Usertags: ftbfs-gcc-14 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2024/07/01/jnettop_0.13.0-1.2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-14/porting_to.html [...] checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether x86_64-linux-gnu-gcc accepts -g... yes checking for x86_64-linux-gnu-gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of x86_64-linux-gnu-gcc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E checking for egrep... grep -E checking for ANSI C header files... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/sockio.h usability... no checking sys/sockio.h presence... no checking for sys/sockio.h... no checking for wbkgdset in -lncurses... yes checking ncurses.h usability... yes checking ncurses.h presence... yes checking for ncurses.h... yes checking ncurses/ncurses.h usability... no checking ncurses/ncurses.h presence... no checking for ncurses/ncurses.h... no checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking db.h usability... no checking db.h presence... no checking for db.h... no checking for db_create in -ldb... no checking for an ANSI C-conforming const... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for gethostbyname... yes checking for connect... yes checking for extraneous pcap header directories... found -- -I/usr/include/pcap -I/usr/include added to CFLAGS checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking for pcap_open_live in -lpcap... yes checking if pcap_freecode takes 2 arguments... no checking if pcap_freecode takes 1 argument... yes checking if struct in6_addr contains s6_addr32 member... yes checking if "localhost" resolves... no configure: error: can't figure out gethostbyname_r() since localhost doesn't resolve make: *** [debian/rules:29: config.status] Error 1 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---Version: 0.13.0-2 jnettop (0.13.0-2) unstable; urgency=medium ... * d/p/0005: Don't require gethostbyname("localhost") to work, this is not actually used anywhere later ... -- наб <[email protected]> Sun, 08 Dec 2024 21:48:43 +0100
--- End Message ---
