Your message dated Sat, 15 Sep 2012 19:26:23 +0200 with message-id <20120915172623.gj5...@radis.cristau.org> and subject line Re: Bug#675447: nmu: netcdf_1:4.1.3-6 has caused the Debian Bug report #671965, regarding etsf-io: FTBFS: configure: error: "No 'NetCDF' library found." 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.) -- 671965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: etsf-io Version: 1.0.3-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > debian/rules build > test -x debian/rules > mkdir -p "." > echo 5 >debian/compat > touch debian/stamp-autotools-files > chmod a+x /«PKGBUILDDIR»/./configure > mkdir -p . > cd . && CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat > -Werror=format-security -Wall" CXXFLAGS="-g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall" > CPPFLAGS="-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" > /«PKGBUILDDIR»/./configure --build=x86_64-linux-gnu --prefix=/usr > --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" > --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var > --libexecdir="\${prefix}/lib/etsf-io" --srcdir=. --disable-maintainer-mode > --disable-dependency-tracking --disable-silent-rules > --docdir=\${prefix}/share/doc/libetsf-io-doc --with-moduledir=\${includedir} > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking for gfortran... gfortran > checking for Fortran compiler default output file name... a.out > checking whether the Fortran 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 Fortran compiler... yes > checking whether gfortran accepts -g... yes > checking for Fortran flag to compile .f90 files... none > checking whether we are using the GNU Fortran compiler... (cached) yes > checking whether gfortran accepts -g... (cached) yes > checking which type of Fortran compiler we have... gcc GNU > checking whether the Fortran compiler accepts exit()... yes > checking whether the Fortran compiler accepts flush()... yes > checking for module extension for compiler 'gcc'... mod > checking for ranlib... ranlib > checking for ar... ar > checking for /usr/include/netcdf.mod... yes > configure: error: "No 'NetCDF' library found." > checking for netcdf library... no > LDFLAGS was '-Wl,-z,relro' > Action: install NetCDF and set the library link path with > --with-netcdf-ldflags. > make: *** [debian/stamp-autotools] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/08/etsf-io_1.0.3-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems.
--- End Message ---
--- Begin Message ---On Thu, Aug 30, 2012 at 21:54:53 +0200, Salvatore Bonaccorso wrote: > Hi Cyril > > On Fri, Jun 01, 2012 at 11:48:28AM +0200, Cyril Brulebois wrote: > > Ólafur Jens Sigurðsson <ojs...@gmail.com> (01/06/2012): > > > netcdf is causing FTBS for packages that rely on > > > /usr/include/netcdf.mod because they use gfortran-4.7 but the mod file > > > is built against gfortran-4.6. > > > > we're trying to get that switch reverted, so binNMUing your package > > might not be needed. > > > > > nmu netcdf_1:4.1.3-6 . ALL . -m "Rebuild against gfortran-4.7, see > > > #671965" > > > > That's incorrect anyway, the switch only happened on *{amd64,i386}. > > [I'm not the maintainer of this package but looking at currently open > RC bugs for wheezy.] > > Am I correct, that as now we have (definitively) gcc defaults to 4.7 > for amd64, i386, kfreebsd-amd66 and kfreebsd-i386 a binNMU can be done? > > nmu netcdf_1:4.1.3-6 . amd64,i386,kfreebsd-amd64,kfreebsd-i386 . -m "Rebuild > against gfortran-4.7, see #671965" > Scheduled. Note that architecture names need to be space separated. Cheers, Julien
signature.asc
Description: Digital signature
--- End Message ---
