Posted by
Brad-11 on
URL: http://quantlib.414.s1.nabble.com/quantlib-python-compile-error-tp4088p4096.html
Dirk Eddelbuettel <edd <at> debian.org> writes:
>
> 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 ...
Ok, I tried to see how compiler-gcc.h gets included. Here it is:
/usr/include/python2.3/Python.h includes
/usr/include/pth.h includes
/usr/include/sys/signal.h includes
/usr/include/signal.h includes
/usr/include/bits/sigcontext.h includes
/usr/include/asm/sigcontext.h includes
/usr/include/linux/compiler.h includes
/usr/include/linux/compiler-gcc3.h includes
/usr/include/linux/compiler-gcc.h
Hope this helps. That last one is the one with the offending macro in it.
> | The unit tests (python setup.py test) hang after testing build_ext, but
> | maybe that's an unrelated problem.
Just for the record: This problem was totally unrelated. The problem was between
keyboard and chair for that one... I am too embarrassed to talk about it. The
unit tests run fine now.