Boost C++ Libraries: Ticket #8499: improving pgi support https://svn.boost.org/trac10/ticket/8499 <p> I have access to PGI 12.2 and 12.5 on a Cray XE6 system. The current boostcpp.jam specifically doesn't build "versioned" .so files on PGI (and there's a comment in the file that indicates they don't work). However, it appears to work for me. To be fair, I don't know if it's due to changes in the compiler versions since pgi.jam was developed or if some of my other pgi.jam changes fascillitated this in some way. I am not very familiar with jamfiles... I modified my changes based on cray.jam and gcc.jam, but this appears to be working for me. </p> <p> My second change is specifically to better support PGI on Cray systems. Cray's compiler wrappers automatically scan the commandline looking for the "-shared", "-static", "-Bshared", and "-Bstatic" to detect if the userswe is attempting to compile dynamically or statically (and adds additional options as necessary). These wrappers consider it an error to find both a "static" and a "shared" flag on the same command line. pgi.jam does this using the -Bst coatic/-Bshared flags to control linking behavior. However, if these options are passed as -Wl,-Bstatic... this won't trigger the error condition in the compiler wrappers, and (of course) passes the option through to ld(1). I believe this is a reasonable changes for non-Cray systems. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/8499 Trac 1.4.3 alan@… Fri, 26 Apr 2013 04:26:19 GMT attachment set https://svn.boost.org/trac10/ticket/8499 https://svn.boost.org/trac10/ticket/8499 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">boost_1_53_0-cray.pgi.diff</span> </li> </ul> <p> pgi.jam improvements </p> Ticket