Re: [C++-sig] _POSIX_C_SOURCE redefinition warning with python 2.3and boost-1.31.0
Thanks Dave. Here is what I am getting on my console when I am trying to compile Boost. On googling I found that I am getting this warning because, of the importance of include order for Python header files. Should I ignore these warnings? or what I can do to get rid of these warnings ? Also due to unfamiliarity with CVS , I have to ask this rather stupid question. When you say Revision_1_31_0 does it mean it is a tag or branch in CVS ? I believe in Boost RC_n_n_n stands for release version and there is a separate tag Version_n_n_n. Thanks in advance. ~Ashish /usr/local/include/python2.3/pyconfig.h:856:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/limits.h:26, from /usr/lib/gcc/i386-redhat-linux/3.4.3/include/limits.h:122, from /usr/lib/gcc/i386-redhat-linux/3.4.3/include/syslimits.h:7, from /usr/lib/gcc/i386-redhat-linux/3.4.3/include/limits.h:11, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/detail/wrap_python.hpp:27, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/detail/prefix.hpp:13, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/type_id.hpp:9, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/converter/registry.hpp:8, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/libs/python/build/../src/converter/registry.cpp:6: /usr/include/features.h:150:1: warning: this is the location of the previous definition
aashish@iastate.edu writes:
Thanks Dave.
Here is what I am getting on my console when I am trying to compile Boost.
On googling I found that I am getting this warning because, of the importance of include order for Python header files.
Right.
Should I ignore these warnings?
Probably not. This is a question for the Python developers really.
or what I can do to get rid of these warnings ?
Boost 1.32.0 shouldn't give you the warnings. As for 1.31.0, the only thing I can suggest is that you steal boost/python/detail/prefix.hpp, boost/python/detail/wrap_python.hpp, and boost/python/detail/config.hpp from 1.32.0, and make sure you start all of your source files with #include <boost/python/detail/prefix.hpp>
Also due to unfamiliarity with CVS , I have to ask this rather stupid question. When you say Revision_1_31_0 does it mean it is a tag or branch in CVS ?
Branches are a special kind of tag; they're identified the same way.
I believe in Boost RC_n_n_n stands for release version
No, it stands for release candidate.
and there is a separate tag Version_n_n_n.
That's the tag for the actual release. -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
aashish@iastate.edu writes:
Thanks Dave.
Here is what I am getting on my console when I am trying to compile Boost.
On googling I found that I am getting this warning because, of the importance of include order for Python header files.
Right.
Should I ignore these warnings?
Probably not. This is a question for the Python developers really.
or what I can do to get rid of these warnings ?
Boost 1.32.0 shouldn't give you the warnings. As for 1.31.0, the only thing I can suggest is that you steal boost/python/detail/prefix.hpp, boost/python/detail/wrap_python.hpp, and boost/python/detail/config.hpp from 1.32.0, and make sure you start all of your source files with
#include <boost/python/detail/prefix.hpp>
Here is another suggested work-around. It involves changing pyconfig.h: http://mail.python.org/pipermail/c++-sig/2005-April/008776.html Maybe it is easier to apply. Are you sure you can't switch to Boost 1.32? Andreas
Thanks again Dave and Andreas. I am giving 1.32.0 a try and yes I didn't get those warnings with this version. So now I am going to try compiling other library (VRJuVRJugglersion 2.0 alpha4 ) with new boost version. If it does not work I will try Dave's or your suggestion. Also I think I created two threads on the same subject. I am sorry about that as something went wrong with my email. ~Regards, AshiAshish --- Andreas Beyer <beyebeyer-imbajena deote:
David AbraAbrahamste:
aashaashishtiastate edutes:
Thanks Dave.
Here is what I am getting on my console when I am trying to compile Boost.
On googgooglingound that I am getting this warning because, of the importance of include order for Python header files.
Right.
Should I ignore these warnings?
Probably not. This is a question for the Python developers really.
or what I can do to get rid of these warnings ?
Boost 1.32.0 shouldn't give you the warnings. As for 1.31.0, the only thing I can suggest is that you steal boost/python/detail/prefix.hpp,hpp boost/python/detail/wrap_python.hpp,hpp >and boost/python/detail/confconfig hppm 1.32.0, and make sure you start all of your source files with
#include <boost/python/detail/prefix.hpp>hpp >
Here is another suggested work-around. It involves changing pycopyconfig
httphttpail.python.org/pipepipermail-sig/sig5-April/008776.htmlhtmlMaybe it is easier to apply.
Are you sure you can't switch to Boost 1.32?
Andreas
_______________________________________________ C++-sig sigling list C++-sig@sighon.org httphttpail.python.org/mailman/listlistinfo-sig sig
__________________________________ Discover Yahoo! Use Yahoo! to plan a weekend, have fun online and more. Check it out! http://discover.yahoo.com/
These warnings went away for me when I moved #include <boost/python.hpp> to the top of each file rather than starting with system includes. Neil
Neil Hodgson <nyamatongwe@gmail.com> writes:
These warnings went away for me when I moved #include <boost/python.hpp> to the top of each file rather than starting with system includes.
You always have to start with a Boost.Python #include if you are using Boost.Python (because Python itself imposes that rule and we have to wrap the Python.h header). I assumed the OP was doing that already. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (5)
-
aashish＠iastate.edu -
Andreas Beyer -
Ashish Chaudhary -
David Abrahams -
Neil Hodgson