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

Bug#121698: fails to bulid from source on alpha

[ Sorry, resending 2nd time, I am having a slow morning. Should be fixed now ]

  Ivan> Package: quantlib-python
  Ivan> Version: 0.2.0-3
  Ivan> Severity: serious

  Ivan> There was an error while trying to autobuild your package:
  Ivan> copying QuantLib/__init__.py -> build/lib.linux-alpha-2.1/QuantLib
  Ivan> copying QuantLib/QuantLib.py -> build/lib.linux-alpha-2.1/QuantLib
  Ivan> copying QuantLib/defaults.py -> build/lib.linux-alpha-2.1/QuantLib
  Ivan> running build_ext
  Ivan> my_init_posix: changing gcc to g++
  Ivan> building 'QuantLib.QuantLibc' extension
  Ivan> creating build/temp.linux-alpha-2.1
  Ivan> g++ -g -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/local/include -I/usr/include/python2.1 -c QuantLib/quantlib_wrap.cpp -o build/temp.linux-alpha-2.1/quantlib_wrap.o
  Ivan> g++ -shared build/temp.linux-alpha-2.1/quantlib_wrap.o -lQuantLib -o build/lib.linux-alpha-2.1/QuantLib/QuantLibc.so
  Ivan> touch build-stamp
  Ivan> /usr/bin/fakeroot debian/rules binary-arch
  Ivan> python2.1 setup.py test
  Ivan> Testing step condition options ... ok
  Ivan> Testing barrier option pricer ... ok
  Ivan> Testing binary option pricer ... make: *** [test-stamp] Floating point exception

Hm, I think I would need help from both the Alpha crowd, and upstream (Hi
Nando, Hi Luigi :) here.  Why would running this trigger a floating point

  Ivan> A full build log can be found at:
  Ivan> http://buildd.debian.org/build.php?arch=alpha&pkg=quantlib-python&ver=0.2.0-3

Yes, and the build log for the other architectures for quantlib-python can be
accessed at :

It appears to fail for a vast number of architectures (alpha, arm, hppa,
ia64, m68k, mips, mipsel) though 0.1.9 compiled on arm and mipsel.


Better to have an approximate answer to the right question than a precise 
answer to the wrong question.  --  John Tukey as quoted by John Chambers

Reply to: