Re: Re: quantlib-python compile error

Posted by Dirk Eddelbuettel on
URL: http://quantlib.414.s1.nabble.com/quantlib-python-compile-error-tp4088p4095.html

On 5 October 2005 at 16:57, Brad wrote:
| Thanks, I tried putting the #undef just in front of the #include statement that
| pulled in the file with the "Real barrier() const;" declaration, and put the
| macro back in directly after that.
|
| Here is a diff in case anyone else runs into this problem.
| 1878,1880d1877
| < #ifdef barrier
| < #undef barrier
| < #endif
| 1882d1878
| < #define barrier() __asm__ __volatile__("": : :"memory"

How do you end up with the include but nobody else does? Can you backtrack
and see who calls what to end up with it?  If it is an internal header file
for the kernel then there is no point including it ...

| The unit tests (python setup.py test) hang after testing build_ext, but maybe
| that's an unrelated problem.

I had that for a while on Debian often need to disable TermStructureTest and
InstrumentTest in tests/QuantLibTestSuite.py.  

Hth, Dirk

--
Statistics: The (futile) attempt to offer certainty about uncertainty.
         -- Roger Koenker, 'Dictionary of Received Ideas of Statistics'