Bug#816101: petsc: FTBFS on mipsel - broken openmpi breaks petsc build
Drew Parsons
dparsons at debian.org
Tue Apr 5 11:01:16 UTC 2016
block 816101 by 818909
severity 816101 important
retitle 816101 FTBFS on mipsel - broken openmpi breaks petsc build
thanks
openmpi on mips seems to be in a sorry state at the moment.
Indeed, even though the petsc builds halts on the fortran test, there
is an mpicc segfault earlier in the log at "TESTING: checkCCompiler":
================================================================================
TEST checkCCompiler from config.setCompilers(/«PKGBUILDDIR»/config/BuildSystem/config/setCompilers.py:538)
TESTING: checkCCompiler from config.setCompilers(/«PKGBUILDDIR»/config/BuildSystem/config/setCompilers.py:538)
Locate a functional C compiler
Checking for program /usr/local/sbin/mpicc...not found
Checking for program /usr/local/bin/mpicc...not found
Checking for program /usr/sbin/mpicc...not found
Checking for program /usr/bin/mpicc...found
Defined make macro "CC" to "mpicc"
Pushing language C
All intermediate test results are stored in /tmp/petsc-QnNaJd/config.setCompilers
Executing: mpicc -c -o /tmp/petsc-QnNaJd/config.setCompilers/conftest.o -I/tmp/petsc-QnNaJd/config.setCompilers -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 /tmp/petsc-QnNaJd/config.setCompilers/conftest.c
Possible ERROR while running compiler: exit code 35584
stderr:
[mipsel-manda-02:10115] *** Process received signal ***
[mipsel-manda-02:10115] Signal: Segmentation fault (11)
[mipsel-manda-02:10115] Signal code: Address not mapped (1)
[mipsel-manda-02:10115] Failing at address: 0x1aadf988
[mipsel-manda-02:10115] *** End of error message ***
Segmentation fault
I'm downgrading this bug to "Important" since it will clear as soon as
Bug#818909 is fixed (i.e. the bug is in openmpi, not in petsc).
More information about the debian-science-maintainers
mailing list