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

Alexander Reichle-Schmehl alexander at schmehl.info
Mon Dec 12 12:45:33 UTC 2011


tags 651452 + patch
tags 651452 + pending
thanks

Hi!

* Alexander Reichle-Schmehl <alexander at schmehl.info> [111209 14:41]:
> However I get now the same FTBFS as originally reported.  I guess we
> call that progress...

I think I solved the problem, however I only found a kind of grude
workarround, not a real solution.

The problem seems to be, that petsc is linked to liblam on sparc, and
therefore the additional linkerflad -llam is needed on that arch.  I
have no idea, why this issue han't shown up on armel, mips, mipsel or
s390, the other arches on which petsc uses lam.  My patch adds the
missing flag on sparc.

A nicer fix would be to some detect automatically, if -llam is needed or
not based upon... uh... Don't know what.


That being said, I uploaded the fix to delayed/4.  Please tell me, if I
should delay it longer.


As you can see I also added libmpich2-dev to the build-conflicts.
That's to prevent FTBFS issues as seen while trying to fix the issue in
the porter chroots (see bug log for details).


Best Regards,
  Alexander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: illuminator-0.11.0-8.2-nmu.diff
Type: text/x-diff
Size: 3474 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20111212/64190f16/attachment.diff>


More information about the debian-science-maintainers mailing list