Hi, For some reason, pushing a new revision to the same branch as used in https://forge.sourceware.org/gcc/gcc/pulls/236, the Forge UI does not pick it up. I then tried to create a new branch and pull request, but it does not appear to be sent either. Sorry if there will be multiple mails for these patches!
I noticed that building GDB and other tools in binutils did not take the path given to --with-zstd into account. In my case, I have a system wide zstd dynamic library, but my build should use a static library instead. I thus, build zstd as a static library and point configure to this location. The feedback on my binutils patch was that I should do the change in the GCC tree and then sync that back to binutils. Changes since v1 (in https://forge.sourceware.org/gcc/gcc/pulls/236): - Unify the interface for the consumers of the macro on ZSTD_CFLAGS and ZSTD_LIBS for the result. - Use lowercase variable names for all local variables. Ok for trunk? Kind regards, Torbjörn Torbjörn SVENSSON (3): config: Expand the shared zstd configure macro gcc: Use shared zstd detection libbacktrace: Use shared zstd detection config/zstd.m4 | 119 ++++++++- gcc/Makefile.in | 4 +- gcc/aclocal.m4 | 2 + gcc/configure | 513 ++++++++++++++++++++++++++++++-------- gcc/configure.ac | 80 +----- libbacktrace/aclocal.m4 | 2 + libbacktrace/configure | 458 ++++++++++++++++++++++++++++++++-- libbacktrace/configure.ac | 5 +- 8 files changed, 965 insertions(+), 218 deletions(-) -- 2.43.0
