Hi Steve, Ah, a rock-and-hard-place problem ...
On 8 April 2005 at 19:43, Steve Langasek wrote: | Package: quantlib-ruby | Version: 0.3.8-1 | Severity: serious | Tags: sid | Justification: FTBFS | | The most recent version of quantlib-ruby has failed to build on mipsel with | multiple source errors: | | make[1]: Entering directory /build/buildd/quantlib-ruby-0.3.8' | g++ -fPIC -Wall -g -O2 -fPIC -O2 -I. -I/usr/lib/ruby/1.8/mipsel-linux -I/usr/lib/ruby/1.8/mipsel-linux -I. -I/usr/include -Wno-uninitialized -Wno-unused -O2 -c quantlib_wrap.cpp | quantlib_wrap.cpp: In function uantLib::Date Date_succ(QuantLib::Date*)': | quantlib_wrap.cpp:1644: error: lusDays' undeclared (first use this function) | quantlib_wrap.cpp:1644: error: (Each undeclared identifier is reported only | once for each function it appears in.) | | A full build log can be found at | <http://buildd.debian.org/fetch.php?&pkg=quantlib-ruby&ver=0.3.8-1&arch=mipsel&stamp=1112768767&file=log&as=raw>. | | The build on mipsel was done against a different version of libquantlib0 | than the (much earlier) builds on other architectures. I presume that the | headers between the two versions are not source-compatible. Correct. That mipsel built is now foobared. Quantlib itself built like a charm on all arches, on the same day. Hadn't seen that in a while. The current version is a release candidate for the upcoming 0.3.9 release. I don't typically make ql-python and ql-ruby release for release candidate. Should I this time for mipsel? Or can this wait til 0.3.9 comes out ? Any advice will be greatly appreciated. Regards, Dirk | | -- System Information: | Debian Release: 3.1 | APT prefers testing | APT policy: (500, 'testing') | Architecture: i386 (i686) | Kernel: Linux 2.6.8-2-686-smp | Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) | | Versions of packages quantlib-ruby depends on: | ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an | ii libgcc1 1:3.4.3-6 GCC support library | pn libruby1.8 Not found. | ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3 -- 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
