Re: [Quantlib-dev] QuantLib-Ruby-0.3.3 bug report and building assistance.

[Luigi B. <lui...@fa...>]

Hi Liguo,

On 2003.10.30 22:12, Liguo Song wrote:
> 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

Ouch.
(aside: you shouldn't need that step, though. The SWIG-generated file  
is included in the tarball. You can start from "ruby setup.py build".)
 
> Second, does the test suite of QuantLib-Ruby require something like  
> cppunit to run? If so, where can I get it?

You need the Test::Unit framework. You can get it from  
<http://testunit.talbott.ws>. You'll need version 0.1.8 or above.

> 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?

Hmm. I'll look into it. There's probably some way to tell autoconf to  
add a prefix to the macro names.

Thanks,
	Luigi