I would like to have some more inline comments on the whole static/dynamic/shared linker/compiler flags setup inside cray.jam. Otherwise the patch is just fine. I just remembered the "link" is used for executables, "archive" is the rule for static linking. Sorry for me being off-track.
And an another question: Do we need to be backward-compatible?

As regards backwards compatibility; there is nothing here that would break anything that used to work, but there are enough issues with the existing cray.jam that some cray users have been devising their own build scripts, or their own localized .jam files. That said, we are really targeting the 8.2 and 8.3 versions of the cray C/C++ compiler that incorporate a lot of relevant bug fixes and C++11 support.

On Dec 10, 2013, at 2:50 AM, Jürgen Hunold [email protected] wrote:

I would like to have some more inline comments on the whole static/dynamic/shared linker/compiler flags setup inside cray.jam. Otherwise the patch is just fine. I just remembered the "link" is used for executables, "archive" is the rule for static linking. Sorry for me being off-track.
And an another question: Do we need to be backward-compatible?

—
Reply to this email directly or view it on GitHub.