Your message dated Sun, 9 Mar 2008 17:03:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line failure not reproducible in the same conditions
has caused the Debian Bug report #467586,
regarding libmesh: FTBFS: checking for C++ compiler default output file name... 
configure: error: C++ compiler cannot create executables
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.)


-- 
467586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467586
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libmesh
Version: 0.6.1.dfsg-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080225 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp 
> QUILT_PATCHES=debian/patches quilt pop -a -R || test $? = 2
> No patch removed
> [ ! -f Make.common ] || /usr/bin/make distclean
> rm -f config.sub config.guess
> dh_clean  --exclude ./contrib/triangle/makefile.orig --exclude 
> ./contrib/tetgen/makefile.orig
>  dpkg-source -b libmesh-0.6.1.dfsg
> dpkg-source: building libmesh using existing libmesh_0.6.1.dfsg.orig.tar.gz
> dpkg-source: building libmesh in libmesh_0.6.1.dfsg-3.diff.gz
> dpkg-source: warning: ignoring deletion of file config.guess
> dpkg-source: warning: ignoring deletion of file config.sub
> dpkg-source: building libmesh in libmesh_0.6.1.dfsg-3.dsc
>  debian/rules build
> dh_testdir
> cp /usr/share/misc/config.guess .
> cp /usr/share/misc/config.sub .
> QUILT_PATCHES=debian/patches quilt push -a || test $? = 2
> Applying patch contrib.patch
> patching file contrib/Makefile
> 
> Applying patch numeric_vector.patch
> patching file src/numerics/numeric_vector.C
> 
> Now at patch numeric_vector.patch
> PETSC_DIR=/usr/lib/petsc PETSC_ARCH=linux-gnu-c-opt 
> LDFLAGS=-Wl,-soname,libmesh.so.0.6.1,-lpetsc,-lpetscdm,-lpetscksp,-lpetscmat,-lpetscsnes,-lpetscts,-lpetscvec
>  ./configure --host=i486-linux-gnu --build=i486-linux-gnu --prefix=/usr 
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info 
> --disable-laspack --disable-slepc --disable-sfc --disable-gzstreams 
> --disable-tecplot --disable-metis --disable-parmetis --disable-tetgen 
> --disable-triangle --with-mpi=/usr --with-cxx=mpicxx --with-cc=mpicc 
> --with-f77=mpif77 --disable-gmv
> ---------------------------------------------
> ----------- Configuring libMesh -------------
> ---------------------------------------------
> checking build system type... i486-pc-linux-gnu
> checking host system type... i486-pc-linux-gnu
> checking target system type... i486-pc-linux-gnu
> checking for i486-linux-gnu-g++... mpicxx
> checking for C++ compiler default output file name... configure: error: C++ 
> compiler cannot create executables
> See `config.log' for more details.
> make: *** [config.status] Error 77

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/02/25

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 containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Hi,

While rebuilding in the exact same conditions (except the chroot was
updated to current sid, of course), I could not reproduce the failure,
so the bug has probably been fixed by some changes in another package.

I'm closing this bug (or those bugs, since that mail was sent to all the
bugs in that case).

Lucas


--- End Message ---

Reply via email to