public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103166] [12 regression] wrong dependency on getentropy on newlib-based targets
Date: Tue, 07 Mar 2023 10:24:20 +0000 [thread overview]
Message-ID: <bug-103166-4-idIOZl42VG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103166-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103166
--- Comment #10 from Christophe Lyon <clyon at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> (In reply to Christophe Lyon from comment #0)
> > Maybe there's something wrong with the detection of HAVE_GETENTROPY in
> > configure?
>
> We only do a compile test, not link, so if newlib declares it in <unistd.h>
> but doesn't define it, we detect it incorrectly. But we avoid link tests in
> configure, because there are problems for cross-compilers.
Why do we avoid link tests? Is that because of something like
https://lists.gnu.org/archive/html/autoconf/2007-03/msg00085.html ?
Also I am not sure to understand how this patch fixed the problem?
Before and after this patch we are happy if compilation succeeds, right?
What does the "OR_LINK" part gives us?
next prev parent reply other threads:[~2023-03-07 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 9:05 [Bug libstdc++/103166] New: " clyon at gcc dot gnu.org
2021-11-10 9:33 ` [Bug libstdc++/103166] " pinskia at gcc dot gnu.org
2021-11-10 9:43 ` redi at gcc dot gnu.org
2021-11-11 2:35 ` sandra at gcc dot gnu.org
2021-11-12 17:15 ` hp at gcc dot gnu.org
2021-11-12 19:02 ` redi at gcc dot gnu.org
2021-11-12 20:25 ` hp at gcc dot gnu.org
2021-11-13 0:46 ` cvs-commit at gcc dot gnu.org
2021-11-13 0:50 ` hp at gcc dot gnu.org
2021-11-13 0:58 ` hp at gcc dot gnu.org
2023-03-07 10:24 ` clyon at gcc dot gnu.org [this message]
2023-03-07 11:20 ` redi 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-103166-4-idIOZl42VG@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).