[Boost-bugs] [Boost C++ Libraries] #8499: improving pgi support

Subject: [Boost-bugs] [Boost C++ Libraries] #8499: improving pgi support
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-04-26 04:25:35

#8499: improving pgi support
 Reporter: alan@… | Type: Bugs
   Status: new | Milestone: To Be Determined
Component: Building Boost | Version: Boost 1.52.0
 Severity: Problem | Keywords:
 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.

 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.

Ticket URL: <https://svn.boost.org/trac/boost/ticket/8499>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:12 UTC