[C++-sig] Boost.Pyton v2 & gcc 2.95.3

[David Abrahams]

From: "Hugo van der Merwe" <hugo at adept.co.za>

> On Fri, Aug 30, 2002 at 05:06:54PM +0800, Joel de Guzman wrote:
> <SNIP>
> > # define BOOST_PP_ITERATION_PARAMS_1 (3, (1, BOOST_PYTHON_MAX_ARITY,
> > <boost/python/detail/make_tuple.hpp>))
> > # include BOOST_PP_ITERATE()
>
> I'm getting compile errors on lines like that last one:
>
> `#include' expects "FILENAME" or <FILENAME>
>
> ... ideas?

What platform are you compiling on/targeting?
So far, we've been testing with various gcc versions from 2.95.4 to 3.2
without problems.

> I currently have gcc 2.95.4 installed as default gcc, but I also have
> gcc 3.1 and 3.2 on my system - how do I tell bjam to use gcc3.2 instead
> of straight /usr/bin/gcc ?

Just follow the directions at:
http://www.boost.org/tools/build/gcc-tools.html

If you want to build with multiple GCC versions, you could add an
additional toolset to your BOOST_BUILD_PATH. For example, I have added a
gcc-3.0.4-tools.jam on my local machine which looks like:

# gcc-3.0.4-tools.jam
{
    local GCC_ROOT_DIRECTORY = c:/cygnus/usr/local/gcc-3.0.4 ;
    local GCC_STDLIB_DIRECTORY =
c:/cygnus/usr/local/gcc-3.0.4/lib/gcc-lib/i686-pc-cygwin/3.0.4 ;
    extends-toolset gcc ;
}

> (Will this fix my problem above

probably not

> , or am I
> missing something else?)

probably, but I don't know what it is. There seems to be some issue with
your preprocessor.

> Am I right in thinking that if I've done the "cvs update -dRP
> -rmpl-development boost/mpl" thing once, I don't have to do it again:
> doing a cvs update -dRP in the boost root directory should update
> everything?

Yep.

-----------------------------------------------------------
           David Abrahams * Boost Consulting
dave at boost-consulting.com * http://www.boost-consulting.com