summaryrefslogtreecommitdiff
path: root/Modules/CMakeFortranCompilerId.F.in
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2010-01-13 08:13:46 -0500
committerBrad King <brad.king@kitware.com>2010-01-13 08:13:46 -0500
commit9ef3f8e82036a28c4f0375ec65eb25864a5240ca (patch)
tree89c769bbe521c239947893501bf43d7bab6545a6 /Modules/CMakeFortranCompilerId.F.in
parent7b106a6fb3431774fb38e39e90a1147118f811a0 (diff)
downloadcmake-9ef3f8e82036a28c4f0375ec65eb25864a5240ca.tar.gz
Restore -rdynamic in Linux build rules
The commit "Drop -rdynamic from Linux build rules" removed default use of the flag on Linux. It was expected to be compatible because any project using plugins should set ENABLE_EXPORTS on its executables to export their symbols for use by the plugins in a cross-platform way. However, it is possible to build without ENABLE_EXPORTS and load plugins that do not link to any symbols from the executable explicitly. These plugins may need to see RTTI and other executable symbols needed by the language implementation. Executables using such plugins were broken by the change. If we want to remove the -rdynamic flag in the future we should do so in a compatible way. At that time we should also remove equivalent flags on other platforms (like -bexpall on AIX). We will either need a policy or an explicit API to disable symbol exports on executables. The primary purpose of the above-mentioned commit was to avoid passing the -rdynamic flag to compilers on Linux that do not support it. In this commit we restore the flag but only on GNU and Intel compilers which are known to support it. See issue #9985.
Diffstat (limited to 'Modules/CMakeFortranCompilerId.F.in')
0 files changed, 0 insertions, 0 deletions