public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/102675] New: [12 regression] Bootstrap fails in libsanitizer: 'MD5_DIGEST_STRING_LENGTH' was not declared in this scope
Date: Sat, 09 Oct 2021 22:26:01 +0000	[thread overview]
Message-ID: <bug-102675-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102675
           Summary: [12 regression] Bootstrap fails in libsanitizer:
                    'MD5_DIGEST_STRING_LENGTH' was not declared in this
                    scope
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gerald at pfeifer dot com
                CC: hjl.tools at gmail dot com
  Target Milestone: ---
              Host: *-*-freebsd*
            Target: *-*-freebsd*
             Build: *-*-freebsd*

This happens on all FreeBSD platforms and versions:

CC-HEAD/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp:370
:36: error: 'MD5_CTX' was not declared in this scope
  370 | const unsigned MD5_CTX_sz = sizeof(MD5_CTX);
      |                                    ^~~~~~~


GCC-HEAD/libsanitizer/sanitizer_common/sanitizer_platform_limits_freebsd.cpp:371
:36: error: 
'MD5_DIGEST_STRING_LENGTH' was not declared in this scope; did you mean 
'SHA256_DIGEST_STRING_LENGTH'?
  371 | const unsigned MD5_return_length = MD5_DIGEST_STRING_LENGTH;
      |                                    ^~~~~~~~~~~~~~~~~~~~~~~~
      |                                    SHA256_DIGEST_STRING_LENGTH


It was introduced by commit 2e3d50c09519d1b4899845b21843bae66ecffc2f
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed Oct 6 10:24:24 2021 -0700

    libsanitizer: Merge with upstream

    Merged revision: fdf4c035225de52f596899931b1f6100e5e3e928


I believe the problem is that this adds #include <md5.h> and some
dependencies on constants defined in FreeBSD's /usr/include/md5.h,
where GCC features it's on $GCC_SOURCE/include/md5.h which does not
provide the required constants and types.

             reply	other threads:[~2021-10-09 22:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09 22:26 gerald at pfeifer dot com [this message]
2021-10-09 22:31 ` [Bug bootstrap/102675] " hjl.tools at gmail dot com
2021-10-10 21:04 ` gerald at pfeifer dot com
2021-10-10 21:22 ` hjl.tools at gmail dot com
2021-10-10 21:50 ` hjl.tools at gmail dot com
2021-10-11  9:03 ` rguenth at gcc dot gnu.org
2021-10-22 19:08 ` kargl at gcc dot gnu.org
2021-10-22 20:11 ` hjl.tools at gmail dot com
2021-10-23 13:25 ` hjl.tools at gmail dot com
2021-10-23 17:24 ` gerald at pfeifer dot com
2021-10-23 17:31 ` hjl.tools at gmail dot com
2021-10-23 17:45 ` gerald at pfeifer dot com
2021-10-23 17:46 ` gerald at pfeifer dot com
2021-10-23 18:12 ` hjl.tools at gmail dot com
2021-10-30 20:47 ` gerald at pfeifer dot com
2021-10-30 20:54 ` hjl.tools at gmail dot com
2021-11-12  1:08 ` pinskia at gcc dot gnu.org
2021-11-16 11:40 ` jakub at gcc dot gnu.org
2021-11-16 16:02 ` gerald at pfeifer dot com
2021-11-16 18:12 ` unlvsur at live dot com
2021-11-17 13:03 ` gerald at pfeifer dot com
2021-11-18  9:08 ` cvs-commit at gcc dot gnu.org
2021-11-18  9:18 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-102675-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).