Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2185: bjam hangs when building libs/python/examples/quickstart under MacOS X
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-09-28 00:46:18
#2185: bjam hangs when building libs/python/examples/quickstart under MacOS X
----------------------------------------+-----------------------------------
Reporter: konrad.hinsen@⦠| Owner: grafik
Type: Bugs | Status: new
Milestone: Boost 1.37.0 | Component: Python
Version: Boost Development Trunk | Severity: Showstopper
Resolution: | Keywords:
----------------------------------------+-----------------------------------
Comment (by jamestwebber@â¦):
I'm having the exact problem that meowsqueak reports: bjam hanged after
{{{darwin.link.dll bin/darwin-4.2.1/debug/extending.so}}}
But I can run test_extending.py fine after killing the command and export
the relevant variables. No new wrinkles from what's been previously
reported, but wanted to add another data point.
I'm using OS X 10.7.5 and python 2.7.3 built with homebrew, boost 1.50.0
and bjam built locally from boost.
Digging a bit into the commands, I can see as dave did that Python is
running, with the command
{{{
"/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/bin/python"
"test_extending.py" >
"bin/test_ext.test/darwin-4.2.1/debug/test_ext.output" 2>&1
}}}
But when I run that command alone (after compiling) it runs fine. The
test_ext.output looks fine except that it starts with the characters
`\E[?1034h `which appears to be related to some weird behavior from
readline (CAPTCHA isn't working so I can't post this link, but: search for
"readline+1034h")? I have no idea if that might cause a problem--I'm not
sure how it would.
If I kill the Python process it remains hanging, but killing the bash
script stops the test (which then fails because the output is wrong).
== Actually... ==
I tried running the testing script manually, by pasting this into the
terminal:
{{{
/bin/sh -c
DYLD_LIBRARY_PATH="/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib:/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config:/usr/local/boost_1_51_0/bin.v2/libs/python/build/darwin-4.2.1/debug:/usr/local/boost_1_51_0/libs/python/example/quickstart/bin/darwin-4.2.1/debug:$DYLD_LIBRARY_PATH"
export DYLD_LIBRARY_PATH
PYTHONPATH="bin/darwin-4.2.1/debug"
export PYTHONPATH
"/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/bin/python"
"test_extending.py" >
"bin/test_ext.test/darwin-4.2.1/debug/test_ext.output" 2>&1
status=$?
echo >> "bin/test_ext.test/darwin-4.2.1/debug/test_ext.output"
echo EXIT STATUS: $status >>
"bin/test_ext.test/darwin-4.2.1/debug/test_ext.output"
if test $status -eq 0 ; then
cp "bin/test_ext.test/darwin-4.2.1/debug/test_ext.output"
"bin/test_ext.test/darwin-4.2.1/debug/test_ext"
fi
verbose=1
if test $status -ne 0 ; then
verbose=1
fi
if test $verbose -eq 1 ; then
echo ====== BEGIN OUTPUT ======
cat "bin/test_ext.test/darwin-4.2.1/debug/test_ext.output"
echo ====== END OUTPUT ======
fi
exit $status
}}}
The result is that my terminal hangs--I have to close the window and open
a new one. It does successfully run the tests, though, and outputs the
results.
If I omit the last line (`exit $status`), it runs fine and doesn't hang.
So perhaps this is happening because the shell script is exiting out of
the user's bash shell, never returning control to bjam? This doesn't
explain why I didn't see the test.output file before, I guess. And I would
guess that the exit status is good to know. But this might be the cause of
the problem.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/2185#comment:26> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:10 UTC