On 8/22/06, Steve Reinhardt <[EMAIL PROTECTED]> wrote:
That's very bizarre... we have 2.4.3 and have no problems. I'm sure it has more to do with how your Python is installed on your system than what version it is. What OS/distro are you using? Did you install Python from a standard package/rpm or from source? Do you have multiple versions of Python installed on the machine?
There are multiple versions of Python as I needed to install a new one to meet minimum version requirements. It is in a non-standard location (as can be seen in the earlier mail).
The scons script tries to deduce the correct Python directories by querying the Python interpreter that's running scons itself, using what I think are the standard, official methods, so I'd say that at best your Python install is unusual (in which case we'd want to fix our scons scripts to deal with it) and at worst maybe you need to reinstall Python.
It checks the location of the Python interpreter (and finds the 2.4.3 one), but the directory structure created by default (with configure --prefix=...) isn't what the script expects (the python library needs a `config' added to the directory path). Also, this doesn't explain the missing dl, pthreads and util link libraries. This is a linux installation. I'm looking for hidden options that should be defaults, but trying 2.4.2 might be easier. Should I have the --enable-framework option? I've seen many incompatibilities between Python versions (particularly when working with M5), and there will be more in the future. M5 installation needs to support having Python installed in a fixed location so that incompatibilities with the host environment will not arise. It seems like the new Python system will require dynamic linking, which may prevent M5 from working properly in some supercomputing environments. Michael _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
