On Tue, Aug 09, 2005 at 09:40:02PM -0700, Eric Blossom wrote:
> As a side note, I was unable to compile boost 1.32 under OS/X on a
> machine with 768M of RAM. I gave up after a couple of hours. The
> first phase of g++ grew to 2.7 GB while compiling some XML
> serializer or some such.
I recall s
On Wed, Aug 10, 2005 at 12:29:04PM +1200, Moir, Tom wrote:
> I am trying to install the Boost library and get the following error at the
> beginning
>
> skipping Boost.Python library build due to missing or incorrect configuration
>
> couldn't find Python.h in "/usr/local/include/python2.2"
Sorry I got around that problem. WHich of these do I use...
Invoke the build system, specifying the toolset(s) you wish to use, to build
and install. For example for GNU/GCC.
bjam "-sTOOLS=gcc" install
Or if you are interested only in the built libraries you can have them built
and collect
