[Bug bootstrap/102675] [12 regression] Bootstrap fails in libsanitizer: 'MD5_DIGEST_STRING_LENGTH' was not declared in this scope

jakub at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Tue Nov 16 11:40:48 GMT 2021


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102675

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The include/md5.h part of this has been committed as
r12-4936-g44d9d55c6d0e3a1e26427662d30f350a80282634
The other change hasn't been applied from what I can see.

I wonder if we couldn't do instead:
2021-11-16  Jakub Jelinek  <jakub@redhat.com>

        PR bootstrap/102675
        * sanitizer_common/Makefile.am: Use -DUSE_SYSTEM_MD5 in AM_CXXFLAGS
        of sanitizer_platform_limits_freebsd.cpp.
        * sanitizer_common/Makefile.in: Regenerated.

--- libsanitizer/sanitizer_common/Makefile.am.jj        2021-11-05
00:43:22.647623646 +0100
+++ libsanitizer/sanitizer_common/Makefile.am   2021-11-16 12:29:58.574930436
+0100
@@ -17,6 +17,7 @@ AM_CXXFLAGS += -DSANITIZER_LIBBACKTRACE
 endif
 AM_CCASFLAGS = $(EXTRA_ASFLAGS)
 ACLOCAL_AMFLAGS = -I m4
+sanitizer_platform_limits_freebsd.lo: AM_CXXFLAGS += -DUSE_SYSTEM_MD5

 noinst_LTLIBRARIES = libsanitizer_common.la

--- libsanitizer/sanitizer_common/Makefile.in.jj        2021-11-05
00:43:22.647623646 +0100
+++ libsanitizer/sanitizer_common/Makefile.in   2021-11-16 12:30:58.611088913
+0100
@@ -796,6 +796,7 @@ uninstall-am:

 .PRECIOUS: Makefile

+sanitizer_platform_limits_freebsd.lo: AM_CXXFLAGS += -DUSE_SYSTEM_MD5

 # Tell versions [3.59,3.63) of GNU make to not export all variables.
 # Otherwise a system limit (for SysV at least) may be exceeded.

and avoid the need of a local patches for this - the Makefiles are owned by
gcc, not imported from compiler-rt, and we require GNU make for building gcc
AFAIK.


More information about the Gcc-bugs mailing list