Re: [boost] Re: Re: Possible emergency: boost/numeric

From: David Abrahams (dave_at_[hidden])
Date: 2002-09-30 10:57:41

Argh!

The problem was that I installed the Numerical Python package, which puts a
directory called "Numeric" in the Python #include directory. On a regular
windows filesystem, that's the same as "numeric". When building
Boost.Python, of course I need to have the Python #include directory in my
path.

<boost/numeric> is exonerated.

My installation of Numerical Python just happened to coincide with the
ublas checkin.
Sorry to everyone, especially Joerg, for wasting bandwidth without enough
investigation.

-----------------------------------------------------------
           David Abrahams * Boost Consulting
dave_at_[hidden] * http://www.boost-consulting.com

----- Original Message -----
From: "David Abrahams" <dave_at_[hidden]>
To: "Boost mailing list" <boost_at_[hidden]>
Cc: "Joerg Walter" <jrh.walter_at_[hidden]>
Sent: Monday, September 30, 2002 11:35 AM
Subject: Re: [boost] Re: Re: Possible emergency: boost/numeric

> WAIT!
>
> I guess I wasn't thinking clearly. Please don't move the directory until
> I've investigated further.
>
> I now don't see how we were getting a conflict unless $BOOST_ROOT/boost
was
> somehow getting into the #include <...> search path.
> The directory in question is $BOOST_ROOT/boost/numeric, and only
> $BOOST_ROOT should be in the #include<...> path.
>
> I'm going to figure out what's happening.

Well, I can't figure it out.