public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "judge.packham at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/111057] New: build error: libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:180:10: fatal error: crypt.h: No such file or directory
Date: Fri, 18 Aug 2023 00:59:45 +0000	[thread overview]
Message-ID: <bug-111057-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111057
           Summary: build error:
                    libsanitizer/sanitizer_common/sanitizer_platform_limit
                    s_posix.cpp:180:10: fatal error: crypt.h: No such file
                    or directory
           Product: gcc
           Version: 13.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: judge.packham at gmail dot com
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

Hi from crosstool-ng,

I've had a user report a build error for GCC 13.2.0 with and aarch64 config
with libsanitizer enabled
(https://github.com/crosstool-ng/crosstool-ng/issues/2010).

[ERROR]   
/home/ctng/crosstool-ng/.build/aarch64-unknown-linux-gnu/src/gcc/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:180:10:
fatal error: crypt.h: No such file or directory
[ALL  ]      180 | #include <crypt.h>
[ALL  ]          |          ^~~~~~~~~
[ALL  ]    compilation terminated.
[ERROR]    make[5]: *** [Makefile:614: sanitizer_platform_limits_posix.lo]
Error 1
[ERROR]    make[5]: *** Waiting for unfinished jobs....

It looks like this may have already been fixed in master by commit d96e14ceb947
("libsanitizer: merge from upstream (87e6e490e79384a5)"). Is that the kind of
thing that might end up in the 13.x branch? Alternatively is there a lower
impact change that might be back-ported?

Thanks,
Chris

             reply	other threads:[~2023-08-18  0:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  0:59 judge.packham at gmail dot com [this message]
2023-08-18  1:02 ` [Bug sanitizer/111057] " pinskia at gcc dot gnu.org
2023-08-18  1:04 ` pinskia at gcc dot gnu.org
2023-08-18  1:05 ` [Bug sanitizer/111057] [11/12/13 only] " pinskia at gcc dot gnu.org
2023-08-18  1:05 ` pinskia at gcc dot gnu.org
2023-08-18  1:21 ` judge.packham at gmail dot com
2023-08-18  1:47 ` judge.packham at gmail dot com
2024-03-11 21:47 ` romain.geissler at amadeus dot com

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-111057-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).