Source: quantlib-swig
Version: 1.13-5
Severity: normal

Dear Maintainer,

The build fails here:
g++ -shared -O0 -g0 --param ggc-min-expand=20 -DBOOST_NO_AUTO_PTR -Wdate-time 
-D_FORTIFY_SOURCE=2 build/temp.linux-parisc64-3.6/QuantLib/quantlib_wrap.o 
-lQuantLib -o 
build/lib.linux-parisc64-3.6/QuantLib/_QuantLib.cpython-36m-hppa-linux-gnu.so 
-fopenmp
/usr/bin/ld: 
build/temp.linux-parisc64-3.6/QuantLib/quantlib_wrap.o(.text._ZNSt6vectorIN8QuantLib6HandleINS0_5QuoteEEESaIS3_EE14_M_fill_assignEjRKS3_[_ZNSt6vectorIN8QuantLib6HandleINS0_5QuoteEEESaIS3_EE14_M_fill_assignEjRKS3_]+0x12c):
 cannot reach 
000099df__ZNSt6vectorIN8QuantLib6HandleINS0_5QuoteEEESaIS3_EE5beginEv+0, 
recompile with -ffunction-sections
/usr/bin/ld: 
build/temp.linux-parisc64-3.6/QuantLib/quantlib_wrap.o(.text._ZNSt6vectorIN8QuantLib6HandleINS0_5QuoteEEESaIS3_EE14_M_fill_assignEjRKS3_[_ZNSt6vectorIN8QuantLib6HandleINS0_5QuoteEEESaIS3_EE14_M_fill_assignEjRKS3_]+0x12c):
 cannot handle R_PARISC_PCREL17F for 
_ZNSt6vectorIN8QuantLib6HandleINS0_5QuoteEEESaIS3_EE5beginEv
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
error: command 'g++' failed with exit status 1

The full build log is here:
https://buildd.debian.org/status/fetch.php?pkg=quantlib-swig&arch=hppa&ver=1.13-5&stamp=1536156811&raw=0

This error is an indication that the stub table has overflowed and some 
branches can't reach their targets in the stub table.  This could be caused
by too high a call density in quantlib_wrap.o, or a gcc bug, etc.

The work around is to add the "-mlong-calls" option to the build on hppa.
I had a successful build with this option.

Thanks,
Dave Anglin

-- System Information:
Debian Release: buster/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.68+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Reply via email to