aboutsummaryrefslogtreecommitdiff
path: root/missing
diff options
context:
space:
mode:
authorRuslan Kabatsayev <b7.10110111@gmail.com>2022-02-11 20:10:23 +0300
committerAndrew Burgess <aburgess@redhat.com>2022-02-22 14:42:06 +0000
commit6a8fe63330c922255a4ced4b6491d35f6c384bba (patch)
treef6f67d0c007e6659d1a17586ca80525c47dcc7a4 /missing
parent955b0ef98ea757bad1b9be429e4b8d13689da13b (diff)
downloadgdb-6a8fe63330c922255a4ced4b6491d35f6c384bba.zip
gdb-6a8fe63330c922255a4ced4b6491d35f6c384bba.tar.gz
gdb-6a8fe63330c922255a4ced4b6491d35f6c384bba.tar.bz2
gdb: fix detection of compilation and linking flags for source-highlight
Currently there are two problems with the detection of source-highlight via pkg-config in GDB's configure script: 1. The LDFLAGS variable is used to pass the 'pkg-config --libs' output to AC_LINK_IFELSE, which results in the "-L/some/path -lsource-highlight" preceding the conftest.cpp, which can result in a failure to find symbols referenced in conftest.cpp, if the linker is using --as-needed by default. 2. The CFLAGS variable is used to pass the 'pkg-config --cflags' output to AC_LINK_IFELSE. However, as the current language is C++, AC_LINK_IFELSE will actuall use CXXFLAGS, not CFLAGS, so any flags returned from pkg-config will not be seen. This patch fixes both of these mistakes, allowing GDB to correctly configure and build using source-highlight installed into a custom prefix, e.g. ~/opt/gdb-git (because the system version of source-highlight is too old).
Diffstat (limited to 'missing')
0 files changed, 0 insertions, 0 deletions