Your message dated Mon, 21 Oct 2013 06:56:08 +0900 with message-id <20131020215608.ga32...@taihen.jp> and subject line Re: Bug#701444: user-mode-linux: ftbfs with eglibc-2.17 has caused the Debian Bug report #701444, regarding user-mode-linux: ftbfs with eglibc-2.17 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 ow...@bugs.debian.org immediately.) -- 701444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:user-mode-linux Version: 3.2-2um-1 Severity: important Tags: sid jessie User: debian-gl...@lists.debian.org Usertags: ftbfs-glibc-2.17 The package fails to build in a test rebuild on at least amd64 with eglibc-2.17, but succeeds to build with eglibc-2.13. The severity of this report may be raised before the jessie release. The test rebuild was done together with GCC-4.8, so some issues might be caused by the updated GCC as well. arch/um/os-Linux/start_up.c:338:16: error: storage size of 'lim' isn't known The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/user-mode-linux_3.2-2um-1_unstable_gcc48.log The last lines of the build log are at the end of this report. To install eglibc from experimental, apt-get -t experimental install libc6-dev To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev [...] LD arch/um/drivers/mconsole.o CC arch/um/drivers/mmapper_kern.o LD arch/um/drivers/ubd.o CC arch/um/drivers/null.o LD arch/um/drivers/port.o CC arch/um/drivers/pty.o CC arch/um/drivers/tty.o CC arch/um/drivers/xterm.o CC arch/um/drivers/xterm_kern.o LD arch/um/drivers/harddog.o CC arch/um/drivers/cow_user.o CC arch/um/drivers/random.o LD arch/um/drivers/built-in.o CC [M] arch/um/drivers/hostaudio_kern.o LD [M] arch/um/drivers/hostaudio.o CC arch/um/os-Linux/aio.o CC arch/um/os-Linux/execvp.o CC arch/um/os-Linux/file.o CC arch/um/os-Linux/helper.o CC arch/um/os-Linux/irq.o CC arch/um/os-Linux/main.o CC arch/um/os-Linux/mem.o CC arch/um/os-Linux/process.o CC arch/um/os-Linux/registers.o CC arch/um/os-Linux/sigio.o CC arch/um/os-Linux/signal.o CC arch/um/os-Linux/start_up.o arch/um/os-Linux/start_up.c: In function 'check_coredump_limit': arch/um/os-Linux/start_up.c:338:16: error: storage size of 'lim' isn't known struct rlimit lim; ^ arch/um/os-Linux/start_up.c:339:2: error: implicit declaration of function 'getrlimit' [-Werror=implicit-function-declaration] int err = getrlimit(RLIMIT_CORE, &lim); ^ arch/um/os-Linux/start_up.c:339:22: error: 'RLIMIT_CORE' undeclared (first use in this function) int err = getrlimit(RLIMIT_CORE, &lim); ^ arch/um/os-Linux/start_up.c:339:22: note: each undeclared identifier is reported only once for each function it appears in arch/um/os-Linux/start_up.c:347:22: error: 'RLIM_INFINITY' undeclared (first use in this function) if (lim.rlim_cur == RLIM_INFINITY) ^ arch/um/os-Linux/start_up.c:338:16: warning: unused variable 'lim' [-Wunused-variable] struct rlimit lim; ^ cc1: some warnings being treated as errors make[2]: *** [arch/um/os-Linux/start_up.o] Error 1 make[1]: *** [arch/um/os-Linux] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»/linux-source-3.2' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---On Sat, Feb 23, 2013 at 11:35:46AM +0000, Matthias Klose wrote: > Package: src:user-mode-linux > Version: 3.2-2um-1 > Severity: important > Tags: sid jessie > User: debian-gl...@lists.debian.org > Usertags: ftbfs-glibc-2.17 > > The package fails to build in a test rebuild on at least amd64 with > eglibc-2.17, but succeeds to build with eglibc-2.13. The > severity of this report may be raised before the jessie release. The latest upload (3.11-1um) succeeds building in current unstable using libc6-dev=2.17-93 gcc=4:4.8.1-3 So this should also be resolved. Thanks -- mattia :wq!
--- End Message ---
