Bug#651452: illuminator: FTBFS on sparc (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte')

[Adam C Powell IV]

On Thu, 2011-12-15 at 09:55 +0100, Alexander Reichle-Schmehl wrote:
> reopen 651452
> found 651452 0.11.0-12
> thanks
> 
> 
> Hi!
> 
> * Adam C Powell IV <hazelsct at debian.org> [111214 15:33]:
> 
> > Better to rip out the -llam and replace LLAM in the patch with -lmpi.
> > I'll test then upload -12 with this change and let's see how it builds.
> 
> That didn't work, too:  It fails to build on armel, sparc due to that
> precise error (tsview-tsview.o: undefined reference to symbol
> 'lam_mpi_byte').  BTW:  The build-depends in the sid chroot on
> smetana.debian.org, the sparc porter box, are still available.  And the
> machine builds the package quite fast.

Okay.  I don't believe this is an illuminator error.

The issue is that LAM should not be anywhere on the system, nothing
should be linked with it, nothing should use its headers, nothing should
try to link with it.  The lam_mpi_byte symbol is probably a #define in
the LAM headers, which shouldn't even be installed.  libmpich2-dev has
been the mpi-default-dev package on non-openmpi platforms for nearly
seven months, so everything should have been rebuilt against it.

So where is the LAM "contamination" coming from?

I'll log into smetana and see what I can figure out.

> Furthermore it's unbuildable on mips, mipsel and s390 as configure
> doesn't find the PETSc libraries, which looks like the error I described
> in mail #27 of this bug.

The PETSc libraries are installed, and the test is from petsc.m4 . But
we don't know what the linking error is that causes it to fail, could be
the same kind of error as the one in the tsview link.

> > Please don't zero-day NMU!
> 
> Of course.  Just for the record:  When I did a zero-day NMU it was a bug
> of an RC bug without any maintainer reaction for more than 7 days.  So
> the 0-day NMU was covered by the developers reference.  Now that you are
> working on the issue, I can't.

Understood.  The problem is on my end.  I'm afraid since I subscribed to
debian-science-maintainers there's been too much traffic on that list
for me to read, and bug emails which used to come to my address and go
into my "bugs" folder go into that folder instead.  So I had no idea any
of this was happening until I scanned d-s-m 8 days later...

Thanks,
Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools
http://www.opennovation.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20111215/27220665/attachment.pgp>