Login  Register

QuantLib-Ruby-0.3.3 bug report and building assistance.

Posted by Liguo Song on Oct 30, 2003; 1:13pm
URL: http://quantlib.414.s1.nabble.com/QuantLib-Ruby-0-3-3-bug-report-and-building-assistance-tp10407.html

I am building the RPM package for QuantLib-Ruby-0.3.3. As I know nothing about
ruby, so I might need someone with more experience with this package to help me out.

First of all, the bug report:
README.txt:
  line 8: ruby setup.py wrap -> ruby setup.rb wrap

Second, does the test suite of QuantLib-Ruby require something like cppunit to
run? If so, where can I get it?

I encountered the following errors when try to use ruby setup.rb test
*******************************************************************************
        ruby setup.rb test
        Building extension...
        creating Makefile
        make: Nothing to be done for `all'.
        Testing QuantLib-Ruby...
        ./QuantLibTestSuite.rb:17:in `require': No such file to load -- test/unit
(LoadError)
                from ./QuantLibTestSuite.rb:17
                from setup.rb:211:in `load'
                from setup.rb:211
                from setup.rb:206:in `call'
                from setup.rb:137:in `execute'
                from setup.rb:268
*******************************************************************************


Third, when building the QuantLib-Ruby package, there are serveral warnings
about the redefinition of macros. The error messages are like the following:
*******************************************************************************
        In file included from /usr/include/ql/qldefines.hpp:68,
                  from /usr/include/ql/quantlib.hpp:23,
                  from quantlib_wrap.cpp:804:
        /usr/include/ql/config.hpp:98:1: warning: "PACKAGE_BUGREPORT" redefined
        In file included from /usr/lib/ruby/1.6/i386-linux/ruby.h:21,
                  from quantlib_wrap.cpp:28:
        /usr/lib/ruby/1.6/i386-linux/config.h:6:1: warning: this is the location of the
previous definition
*******************************************************************************
Other macros with this problem are PACKAGE_NAME, PACKAGE_STRING,
PACKAGE_TARNAME, and PACKAGE_VERSION.

After some research, I found that these macros are defined in both
/usr/include/ql/config.hpp and /usr/lib/ruby/1.6/i386-linux/config.h. Would this
cause any surprise in the future?

Thanks for your help.


Liguo (Leo)