Your message dated Tue, 27 Nov 2012 00:22:57 +0100
with message-id <50b3f9d1.6090...@debian.org>
and subject line Re: Re: Bug#651452: illuminator: FTBFS on sparc
(tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')
has caused the Debian Bug report #652315,
regarding Get this out of testing until its rdepends have rebuilt
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.)
--
652315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: illuminator
Version: 0.11.0-8.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: Alexander Reichle-Schmehl <toli...@debian.org>
See
https://buildd.debian.org/status/fetch.php?pkg=illuminator&arch=sparc&ver=0.11.0-8.1&stamp=1323062646
> /usr/lib/lam/bin/mpicc -g -O2 -o .libs/tsview tsview-tsview.o
> libluminate/.libs/libluminate.so -lpetsc -lncurses -lhistory -lreadline
> /usr/bin/ld: tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte'
> /usr/bin/ld: note: 'lam_mpi_byte' is defined in DSO /usr/lib/liblam.so.4 so
> try adding it to the linker command line
> /usr/lib/liblam.so.4: could not read symbols: Invalid operation
> collect2: ld returned 1 exit status
> make[3]: *** [tsview] Error 1
Cheers,
Julien
--- End Message ---
--- Begin Message ---
Am 24.11.2012 15:53, schrieb Ivo De Decker:
> On Thu, Dec 15, 2011 at 07:45:47PM -0500, Adam C Powell IV wrote:
>> Found the problem. PETSc built on November 16 with mpi-defaults 0.6
>> which depended on LAM on non-openmpi arches. Now mpi-defaults 1.0.1
>> released 12/4 depends on MPICH2, so we have a mix of architectures
>> installed. And mpi-defaults just went into testing today... Crap!
>>
>> It may be that other PETSc dependencies need rebuilding too... and there
>> are a lot of them! Let's see: suitesparse, spooles, hypre, scotch,
>> blacs-mpi, scalapack, mumps, all have to be rebuilt with MPICH2! What
>> was built when:
>> * suitesparse: April 15 2010
>> * spooles: May 11 2010
>> * hypre: August 15 2010
>> * scotch: April 6 2011
>> * blacs-mpi: August 29 2011
>> * scalapack: September 18 2011
>> * mumps: March 31 2011
>> None was built recently, all need to be rebuilt. mpi-defaults should
>> not be in testing until at least these are rebuilt, probably others.
>>
>> Note: HDF5 is not a problem for PETSc because PETSc only links to it on
>> OpenMPI platforms. I forgot why that is, maybe it's worth a try
>> building PETSc against HDF5-mpich2? Maybe later...
>>
>> Okay, cloning this bug to a bunch of packages, see above. I've been an
>> uploader to all except blacs-mpi and scalapack, and many of them could
>> use some maintenance, this is a good excuse to spend time on them. :-)
>
> Adam,
>
> Is this bug still relevant? All the blocking bugs have been fixed, except
> 651452, which is about illuminator, which is not in testing.
>
> Cheers,
>
> Ivo
I think you meant to send this to #652315, not #651452 right? Anyway, I
checked that all blocking bugs except illuminator are fixed in testing,
so I'm closing this bug.
Best regards,
Tobias
--- End Message ---
