Opened 13 years ago

Closed 12 years ago

#629 closed Bugs (fixed)

boost 1.33.1 build error

Reported by: paulmelis Owned by: Vladimir Prus
Milestone: Component: build
Version: None Severity: Showstopper
Keywords: Cc:

Description (last modified by René Rivera)

When trying to build 1.33.1 with bjam 3.1.12 under
linux (debian, dual AMD opteron, 2.6.11 kernel) I get
the following error output (see attachment for full
output):

Building Boost.Regex with the optional Unicode/ICU
support disabled.
Please refer to the Boost.Regex documentation for more
information
(and if you don't know what ICU is then you probably
don't need it).
Jamfile:278: in load-jamfiles
*** argument error
* rule stage ( name : sources + : requirements * :
local-build * )
* called with: (  :
/home1/rugrchpc/melis/boost_1_33_1/boost/compatibili
[...]
ucket_sorter.hpp
/home1/rugrchpc/melis/boost_1_33_1/boost/pending/fibonacci_heap.hpp
/home1/rugrchpc/melis/boost_1_33_1/boost/pending/iterator_tests.hpp
/home
1/rugrchpc/melis/boost_1_33_1/boost/pending/detail/int_iterator.hpp
/home1/rugrchpc/melis/boost_1_33_1/boost/pending/detail/property.hpp
/home1/rugrchpc/melis
/boost_1_33_1/boost/pending/detail/disjoint_sets.hpp :
<locate>stage
<tree-subdirs>/home1/rugrchpc/melis/boost_1_33_1
<target>all : <suppress>true )
* missing argument name
/home1/rugrchpc/melis/boost_1_33_1/tools/build/v1/boost-base.jam:2330:see
definition of rule 'stage' being called
/home1/rugrchpc/melis/boost_1_33_1/tools/build/v1/bootstrap.jam:21:
in boost-build
/home1/rugrchpc/melis/boost_1_33_1/boost-build.jam:16:
in module scope

I've tried the following build commands:
bjam
bjam "-sTOOLS=gcc"

the results are the same...

1.33.0 builds fine on the same system

Paul

Change History (6)

comment:1 Changed 13 years ago by paulmelis

Logged In: YES 
user_id=548640

added the error output

comment:2 Changed 13 years ago by haution

Logged In: YES 
user_id=618437

I am getting exactly the same problem on RedHat ES4 (2.6.9
kernel) with boost 1.33.1, and boost 1.33.0 also builds fine
on this platform ...

PH

comment:3 Changed 13 years ago by haution

Logged In: YES 
user_id=618437

OK, I painfully found the reason for my problem in the
mailing list :
http://lists.boost.org/Archives/boost/2005/12/98015.php

Andrew Maclean had the same problem on Windows and his
solution worked for me on Linux. 

As he said :
"Maybe a note should be added to the user instructions for
building Boost ... along the line:
If you have any environment variables such as BOOST_INCLUDE,
BOOST_LIB,
BOOST_ROOT, BOOST_VERSION. Delete or rename them before
running bjam."

PH

comment:4 Changed 13 years ago by paulmelis

Logged In: YES 
user_id=548640

Eeeek, I had some of those env vars set because of a
previously installed version of boost. Removing them from
the environment indeed makes boost build!

Funny that 1.33.0 wasn't affected by this though...

comment:5 Changed 13 years ago by az_sw_dude

Logged In: YES 
user_id=579686

Assign to Vladimir -- please reassign if there is a better
boost.build person to look at this.

comment:6 Changed 12 years ago by René Rivera

Component: Nonebuild
Description: modified (diff)
Resolution: Nonefixed
Severity: Showstopper
Status: assignedclosed

This is fixed for Boost 1.34.0 since BBv2 doesn't use env vars, and guards against collisions when it the rare case it does.

Note: See TracTickets for help on using tickets.