Package: slepc
Version: 3.1-p5.dfsg-1
Severity: serious
Tags: wheezy sid
Hi.
Your package fails to build on armel, ia64, mips and sparc. The tail of logs
shows the following error:
> make[1]: Entering directory
> `/build/buildd-slepc_3.1-p5.dfsg-1-armel-p9cLZn/slepc-3.1-p5.dfsg/config'
> /usr/lib/lam/bin/hcp -o checklink.o -c -Wall -Wwrite-strings
> -Wno-strict-aliasing -O -fPIC -g -O2
> -I/usr/lib/petsc/linux-gnueabi-c-opt/include -I/usr/lib/petsc/include
> -I/usr/include -I/usr/lib/lam/include -I/usr/include/scotch
> -I/usr/include/spooles -I/usr/include/suitesparse -I/usr/include/petsc
> -D__INSDIR__=./ checklink.c
> Shared libs in /usr/lib/petsc/linux-gnueabi-c-opt/lib are out of date,
> attempting to rebuild.
> *********************** ERROR ************************
> Unable to rebuild shared libraries; you do not have write permission.
> Libraries were built by user root; please contact him/her to have them
> rebuilt.
> ******************************************************
> make[1]: *** [chkopts] Error 1
> make[1]: Leaving directory
> `/build/buildd-slepc_3.1-p5.dfsg-1-armel-p9cLZn/slepc-3.1-p5.dfsg/config'
> ERROR: Unable to link with PETSc
> Checking environment...
> Checking PETSc installation...
> ERROR: Unable to link with PETSc
> ERROR: See "linux-gnueabi-c-opt/conf/configure.log" file for details
> make: *** [build-arch] Error 1
All build logs are available at:
https://buildd.debian.org/status/package.php?p=slepc
Once the package fixed, it (and its reverse dependencies) will be able to
migrate to testing. Please also note that the status of this transition is
tracker on:
http://release.debian.org/transitions/html/slepc.html
(updated once every hour)
Regards,
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'proposed-updates')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
