[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

petsc 3.7 FTBFS on armhf



Dear arm64 porters, petsc 3.7 (in experimental) fails to build on armhf
(the previous version petsc 3.6 built fine).

The log is 
https://buildd.debian.org/status/fetch.php?pkg=petsc&arch=armhf&ver=3.7.2.dfsg1-1exp1&stamp=1467425583

The build passes configuration, compiles, but failings at the final
linking step:

         CXX arm-linux-gnueabihf-real-debug/obj/src/tao/leastsquares/impls/pounders/gqt.o
         CXX arm-linux-gnueabihf-real-debug/obj/src/tao/leastsquares/impls/pounders/pounders.o
     CLINKER /«PKGBUILDDIR»/arm-linux-gnueabihf-real-debug/lib/libpetsc_real.so.3.7.2
/usr/bin/ld: arm-linux-gnueabihf-real-debug/obj/src/sys/info/verboseinfo.o: relocation R_ARM_THM_MOVW_ABS_NC against `__stack_chk_guard' can not be used when making a shared object; recompile with -fPIC
arm-linux-gnueabihf-real-debug/obj/src/sys/info/verboseinfo.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status

On the face of it, it looks like the build missed an -fPIC flag, but if
that was the problem then I would have expected it to fail the
configuration step.

Does this error message make any sense to you?  

Drew


Reply to: