On Mon, Oct 31, 2005 at 10:15:49AM -0500, Doug Gregor wrote:
I'm CC'ing John Maddock, who is in charge of the config library. It turns out that we're talking about two different "configure" scripts: I was referring to the new one in the Boost root directory, whereas you've found some issues with the one in libs/config. Sorry about the confusion!
Hey Doug, The one in BOOST_ROOT doesn't work on platforms that have a real bourne shell and not bash in disguise (I'm guessing you wrote that on a linux box?). FreeBSD 5.4 doesn't like it, for instance... Bourne shell's comparison is a single =, not ==. diff -r1.3.2.2 configure 73c73 < if test $library == python; then ---
if test $library = python; then
79c79 < if test "x$requested_python" != xyes; then ---
if test "x$requested_python" != "xyes" ; then
93c93 < if test $library == python; then ---
if test $library = python; then
175c175 < if test "x$TOOLSET" == x; then ---
if test "x$TOOLSET" = "x" ; then 182c182 < if test "x$BJAM" == x; then
if test "x$BJAM" = "x" ; then 195c195 < if test "x$flag_show_libraries" == xyes; then
if test "x$flag_show_libraries" = "xyes"; then 213c213 < if test "x$EPREFIX" == x; then
if test "x$EPREFIX" = "x" ; then 217c217 < if test "x$LIBDIR" == x; then
if test "x$LIBDIR" = "x" ; then 221c221 < if test "x$INCLUDEDIR" == x; then
if test "x$INCLUDEDIR" = "x" ; then 226,227c226,227 < if test "x$flag_no_python" == x; then < if test "x$PYTHON_VERSION" == x; then
if test "x$flag_no_python" = "x" ; then if test "x$PYTHON_VERSION" = "x" ; then 233c233 < if test "x$PYTHON_ROOT" == x; then
if test "x$PYTHON_ROOT" = "x" ; then
244,245c244,245 < if test "x$flag_icu" == xyes; then < if test "x$ICU_ROOT" == x; then ---
if test "x$flag_icu" = "xyes"; then if test "x$ICU_ROOT" = "x" ; then
If you run ./configure --with-python=/no/such/python the script still runs to the end, like this: Building Boost.Jam with toolset gcc... tools/build/jam_src/bin.freebsd/bjam Detecting Python version... ./configure: /no/such/python: not found Detecting Python root... ./configure: /no/such/python: not found Unicode/ICU support for Boost.Regex?... no. Generating Makefile... FWIW, it might be nice to specify "#!/bin/sh -e" so that the script would not generate a makefile if there is an error... as far as I got with that is that "tools/build/jam_src/build.sh --guess-toolset" exits with status 1 even though it has correctly determined that the toolset here is "gcc", which then stops "configure". I could poke further if you like... -t