|
We already bumped the minimum SCons version to 2.3.0 in SERVER-16255.
|
|
In the 2.7 timeframe, we should bump the minimum supported SCons version, at least for the enterprise builders.
|
|
Confirmed that it works with a recent version of scons.
$ uname -a
|
Linux client 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
|
$ lsb_release -a
|
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
|
Distributor ID: CentOS
|
Description: CentOS release 6.4 (Final)
|
Release: 6.4
|
Codename: Final
|
|
|
Try with a newer SCons version. An easy way is to clone https://github.com/andy10gen/scons-multi.git, and run the scons script in the root of that repository. It defaults to 2.3.0, but you can override it by setting the SCONS_VERSION environment variable. I think this is the result of a SCons bug, in which case we could just bump the minimum supported SCons version for the enterprise build. What do uname -a and lsb_release -a return?
|
|
schwerin, I'm not sure, but here's the version information from the machine that had this issue:
$ python --version
|
Python 2.6.6
|
$ scons --version
|
SCons by Steven Knight et al.:
|
script: v2.0.1.r5134, 2010/08/16 23:02:40, by bdeegan on cooldog
|
engine: v2.0.1.r5134, 2010/08/16 23:02:40, by bdeegan on cooldog
|
Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 The SCons Foundation
|
|
|
sverch, is this due to the python version, the SCons version, or something else?
|
Generated at Thu Feb 08 03:29:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.