[C++-sig] Preparations for release - linux report

[David Abrahams]

----- Original Message -----
From: "Joseph Koning" <koning at pobox.com>
To: <c++-sig at python.org>
Sent: Saturday, September 28, 2002 10:44 PM
Subject: Re: [C++-sig] Preparations for release - linux report


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> David Abrahams wrote:
>
> |
> |
> |1. Merge everything that's happened on the main trunk of libs/python and
> |boost/python into the RC_1_29_0 branch and test it. I think this just
> |amounts to:
> |
> |    cd $BOOST_ROOT
> |    cvs up -P -d -rRC_1_29_0
> |    cvs up -P -d -jHEAD libs/python boost/python
> |
> I tested the RC_1_29_0 branch against the release22-maint branch on
> linux with the gcc version 3.1 20020619 (Red Hat Linux Rawhide 3.1-6.1)
> compiler.  Here are the results for test:

Joe,

Thanks for testing, but there must be something wrong with your CVS tree,
since there is no file named numpy.cpp in the RC_1_29_0 branch.

...

> ~    g++  -c -Wall -ftemplate-depth-100  -DBOOST_PYTHON_DYNAMIC_LIB
> -DBOOST_PYTHON_V2  -g -O0 -fno-inline -fPIC
> -I"../../../libs/python/test"  -isystem
> "/usr/local/python2.2rel/include/python2.2" -isystem "/var/tmp/boost"
> -o
>
"../../../libs/python/test/bin/numpy_ext.so/gcc/debug/runtime-link-dynamic/
shared-linkable-true/numpy.o"
> "numpy.cpp"
  ^^^^^^^^^^


Or are you saying you have also done the merge step (the line with the -j
option above)?

This doesn't appear to be specific to release22-maint. Do you get the same
error when testing the main trunk of the boost CVS tree?

    cd $BOOST_ROOT
    cvs up -P -d -A
    cd libs/python/test
    bjam ... numpy.obj


Thanks,
Dave


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