Boost logo

Boost :

From: (noreply_at_[hidden])
Date: 2006-11-16 22:46:42

Bugs item #1598141, was opened at 2006-11-16 19:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: build
Group: release 1.34.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: eponym (eponym)
Assigned to: Nobody/Anonymous (nobody)
Summary: top-level configure is broken

Initial Comment:
The top-level configure script in the RC1.34.0 release
is broken.

This script starts out as:


which implies that it is a Bourne-shell script.
But now almost all of tests in the file have been
converted to look like the following:

    220 if test "x$LIBDIR" == x; then
    221 LIBDIR="$EPREFIX/lib"
    222 fi

where (in 1.33.1) they used to look like this:

    217 if test "x$LIBDIR" = "x" ; then
    218 LIBDIR="$EPREFIX/lib"
    219 fi

The problem is that "==" is not a valid Bourne-shell
test-command operator, so the entire build breaks
immediately on any platform which uses a true
Bourne shell as sh.

The fix is to either convert all of these operators
to "=", or to stop claiming the script is a Bourne
shell script and use "#!/bin/bash" instead. But the
latter approach is not recommended because there are
many older machines without bash in that location.


You can respond by visiting:

Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
Boost-bugs mailing list

Boost list run by bdawes at, gregod at, cpdaniel at, john at