I downloaded Boost 1.31.0 and built bjam with the build.sh script. Now, when I try to build boost with bjam -sTOOLS=darwin install, it just hangs, with no output to the console at all. Is there a way to set it into a verbose mode to see what's going on, or does anybody have any idea what's wrong? This is MacOS X 10.3.3 (7G33) on a 12" powerbook G4 (1.33Ghz) with the latest developer tools (7K249). -- Nick
Nick Bastin wrote:
I downloaded Boost 1.31.0 and built bjam with the build.sh script. Now, when I try to build boost with bjam -sTOOLS=darwin install, it just hangs, with no output to the console at all. Is there a way to set it into a verbose mode to see what's going on, or does anybody have any idea what's wrong? This is MacOS X 10.3.3 (7G33) on a 12" powerbook G4 (1.33Ghz) with the latest developer tools (7K249).
You can start by making sure it runs without building anything.. "bjam -v" will output the version info and exit. If that's no problem you can start adding debug options until you get something... "bjam -d<number>" <number> can go from 1 to 13 (I think). That said the immediate question I have is what do you mean by hang? It does take some time before it starts building after you invoke it. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
On May 31, 2004, at 12:27 AM, Rene Rivera wrote:
Nick Bastin wrote:
I downloaded Boost 1.31.0 and built bjam with the build.sh script. Now, when I try to build boost with bjam -sTOOLS=darwin install, it just hangs, with no output to the console at all. Is there a way to set it into a verbose mode to see what's going on, or does anybody have any idea what's wrong? This is MacOS X 10.3.3 (7G33) on a 12" powerbook G4 (1.33Ghz) with the latest developer tools (7K249).
You can start by making sure it runs without building anything.. "bjam -v" will output the version info and exit. If that's no problem you can start adding debug options until you get something... "bjam -d<number>" <number> can go from 1 to 13 (I think).
Ok, so it appears to be in an infinite loop. bjam -d5 prints the following, over and over again: /Users/nbastin/Desktop/boost_1_31_0/tools/build/v1/python.jam:109:
|>>> set PYTHON_FRAMEWORK = /
-- Nick
Nick Bastin wrote:
On May 31, 2004, at 12:27 AM, Rene Rivera wrote:
You can start by making sure it runs without building anything.. "bjam -v" will output the version info and exit. If that's no problem you can start adding debug options until you get something... "bjam -d<number>" <number> can go from 1 to 13 (I think).
Ok, so it appears to be in an infinite loop. bjam -d5 prints the following, over and over again:
/Users/nbastin/Desktop/boost_1_31_0/tools/build/v1/python.jam:109:
|>>> set PYTHON_FRAMEWORK = /
Ouch I see the problem. Try changing line #107 (while $(PYTHON_FRAMEWORK...) to: while $(PYTHON_FRAMEWORK:D=) && $(PYTHON_FRAMEWORK:D=) != Python.framework And tell me if that helps. I'll then fix it CVS. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
On May 31, 2004, at 11:11 AM, Rene Rivera wrote:
Nick Bastin wrote:
On May 31, 2004, at 12:27 AM, Rene Rivera wrote:
You can start by making sure it runs without building anything.. "bjam -v" will output the version info and exit. If that's no problem you can start adding debug options until you get something... "bjam -d<number>" <number> can go from 1 to 13 (I think). Ok, so it appears to be in an infinite loop. bjam -d5 prints the following, over and over again: /Users/nbastin/Desktop/boost_1_31_0/tools/build/v1/python.jam:109:
|>>> set PYTHON_FRAMEWORK = /
Ouch I see the problem. Try changing line #107 (while $(PYTHON_FRAMEWORK...) to:
while $(PYTHON_FRAMEWORK:D=) && $(PYTHON_FRAMEWORK:D=) != Python.framework
And tell me if that helps. I'll then fix it CVS.
That fixes the problem, thanks. -- Nick
participants (2)
-
Nick Bastin -
Rene Rivera