diff options
author | Joseph Myers <joseph@codesourcery.com> | 2023-09-01 15:20:47 +0000 |
---|---|---|
committer | Joseph Myers <joseph@codesourcery.com> | 2023-09-01 15:20:47 +0000 |
commit | 7fdd4fcee1c6698daa8eb5f52017e768b0771503 (patch) | |
tree | d9707c26a835f1f2094aaeb8f4d4e710cc0811cd /config | |
parent | b47a4f92de5c12ac8bdac57b0413e3e05d411832 (diff) | |
download | fsf-binutils-gdb-7fdd4fcee1c6698daa8eb5f52017e768b0771503.zip fsf-binutils-gdb-7fdd4fcee1c6698daa8eb5f52017e768b0771503.tar.gz fsf-binutils-gdb-7fdd4fcee1c6698daa8eb5f52017e768b0771503.tar.bz2 |
config: Fix host -rdynamic detection for build != host != target
[Merge from GCC commit 4d9bc81a5d8d884dee7a7781fa4c1577a6c9681a.]
The GCC_ENABLE_PLUGINS configure logic for detecting whether -rdynamic
is necessary and supported uses an appropriate objdump for $host
binaries (running on $build) in cases where $host is $build or
$target.
However, it is missing such logic in the case where $host is neither
$build nor $target, resulting in the compilers not being linked with
-rdynamic and plugins not being usable with such a compiler. In fact
$ac_cv_prog_OBJDUMP, as used when $build = $host, is always an objdump
for $host binaries that runs on $build; that is, it's appropriate to
use in this case as well.
Tested in such a configuration that it does result in cc1 being linked
with -rdynamic as expected. Also bootstrapped with no regressions for
x86_64-pc-linux-gnu.
config/
* gcc-plugin.m4 (GCC_ENABLE_PLUGINS): Use
export_sym_check="$ac_cv_prog_OBJDUMP -T" also when host is not
build or target.
Diffstat (limited to 'config')
-rw-r--r-- | config/gcc-plugin.m4 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/config/gcc-plugin.m4 b/config/gcc-plugin.m4 index c731a6f..c30cfdd 100644 --- a/config/gcc-plugin.m4 +++ b/config/gcc-plugin.m4 @@ -49,7 +49,7 @@ AC_DEFUN([GCC_ENABLE_PLUGINS], elif test x$host = x$target; then export_sym_check="$gcc_cv_objdump -T" else - export_sym_check= + export_sym_check="$ac_cv_prog_OBJDUMP -T" fi ;; esac |