problem compiling Python bindings under cygwin

[Knox, Matt]

Hi everyone,

after successfully compiling and installing quantlib using cygwin (as far as I can tell anyway), I have moved on to trying to compile and install the python swig wrappers. Near the beginning of the build process (when calling "python setup.py build"), I get the following 4 messages:

gcc: /GR: No such file or directory
gcc: /FD: No such file or directory
gcc: /Zm250: No such file or directory
gcc: /MT: No such file or directory

which may or may not be important. It continues on after that. It chugs along for a while with lots of warnings along the lines of "warning: '__tmp' might be used uninitialized in this function" which I suspect aren't important, and then finally dies with the error: "error: command 'gcc' failed with exit status 1".

The final portion of output before it dies is:

QuantLib/quantlib_wrap.cpp:4779:   instantiated from `static int swig::traits_asptr_stdseq<Seq, T>::
asptr(PyObject*, Seq**) [with Seq = std::vector<std::string, std::allocator<std::string> >, T = std:
:string]'
QuantLib/quantlib_wrap.cpp:4841:   instantiated from `static int swig::traits_asptr<std::vector<T, s
td::allocator<_CharT> > >::asptr(PyObject*, std::vector<T, std::allocator<_CharT> >**) [with T = std
::string]'
QuantLib/quantlib_wrap.cpp:3993:   instantiated from `int swig::asptr(PyObject*, Type**) [with Type
= std::vector<std::string, std::allocator<std::string> >]'
QuantLib/quantlib_wrap.cpp:84672:   instantiated from here
/usr/lib/gcc/i686-pc-mingw32/3.4.4/include/c++/bits/stl_vector.h:715: warning: '__result' might be u
sed uninitialized in this function
/usr/lib/gcc/i686-pc-mingw32/3.4.4/include/c++/bits/stl_tree.h: In member function `typename std::_R
b_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_Link_type std::_Rb_tree<_Key, _Val, _KeyOfValue,
 _Compare, _Alloc>::_M_copy(const std::_Rb_tree_node<_Val>*, std::_Rb_tree_node<_Val>*) [with _Key =
 std::string, _Val = std::pair<const std::string, boost::any>, _KeyOfValue = std::_Select1st<std::pa
ir<const std::string, boost::any> >, _Compare = std::less<std::string>, _Alloc = std::allocator<std:
:pair<const std::string, boost::any> >]':
/usr/lib/gcc/i686-pc-mingw32/3.4.4/include/c++/bits/stl_tree.h:1029: warning: '__top' might be used
uninitialized in this function
/usr/lib/gcc/i686-pc-mingw32/3.4.4/include/c++/bits/stl_tree.h:365: warning: '__tmp' might be used u
ninitialized in this function
error: command 'gcc' failed with exit status 1


Any ideas? I am using python 2.5 and I have successfully compiled other unrelated C extensions for Python with my current setup. Thanks,

- Matt

[Luigi Ballabio]

On Jun 21, 2007, at 8:35 PM, mattknox_ca wrote:

> after successfully compiling and installing quantlib using cygwin (as
> far as
> I can tell anyway), I have moved on to trying to compile and install
> the
> python swig wrappers. Near the beginning of the build process (when
> calling
> "python setup.py build"), I get the following 4 messages:
>
> gcc: /GR: No such file or directory
> gcc: /FD: No such file or directory
> gcc: /Zm250: No such file or directory
> gcc: /MT: No such file or directory

Matt,
        the script is picking up the options for Visual C++.  What happens if
you open a Python interpreter from msys and execute the following?

import sys
print sys.platform

Later,
        Luigi


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users

[Knox, Matt]

> Matt,
> the script is picking up the options for Visual C++.  What happens if
> you open a Python interpreter from msys and execute the following?
>
> import sys
> print sys.platform

sys.platform returns 'win32'. In the setup.py script, is sys.platform really the appropriate thing to check though? Not sure how distutils does things internally, but presumably the behaviour is based on the specified compiler rather than the operating system? I'm not really familiar with writing python setup scripts though, I just use them once someone else has written it :)

[Luigi Ballabio]

On Mon, 2007-06-25 at 10:10 -0700, mattknox_ca wrote:
> sys.platform returns 'win32'. In the setup.py script, is sys.platform really
> the appropriate thing to check though?

Probably not. As you say, it should check the compiler---but I haven't
figured out how to do that yet. Any suggestion, anyone?

Later,
        Luigi


--

Can't act. Slightly bald. Also dances.
-- RKO executive, reacting to Fred Astaire's screen test.
Cerf/Navasky, "The Experts Speak"



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users