From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 871EF3858D3C; Tue,  7 Mar 2023 11:20:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 871EF3858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678188057;
	bh=JrBYjLhgEfB9CUy6HL+L7EmZjdGT26U11z//RgJJFFQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=INiDWP8zH3ivkKcgeuqHHEg7zBrInMr7LnB5S6UTORVH8B6EtQbJw4lYgYXs4DIyl
	 MkKXeqx1P9kaZoNmlcwDZE95/irYReNtxjLvb6D1Rs26yH2n+B1MWg+M69lv81mkGK
	 AafviXImQOBmlIXxCVhA5+mqdUnWLbwKZgVvBu18=
From: "redi 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 11:20:56 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: link-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hp at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 12.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-103166-4-0vgHXUWdFg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-103166-4@http.gcc.gnu.org/bugzilla/>
References: <bug-103166-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #10)
> Why do we avoid link tests? Is that because of something like
> https://lists.gnu.org/archive/html/autoconf/2007-03/msg00085.html ?

No, I don't think it's related to that, but every time somebody explains it=
 to
me I instantly forget the answer.

Here's what Joseph explained last time I asked:

On some bare-metal targets, the compiler can't link unless you explicitly p=
ass
-T or similar options to select a particular BSP.
For any hosted system supporting shared libraries, at least, the cross
configuration ought to be the same as the native configuration (running the
same configure tests), and hardcoding in crossconfig.m4 tends to be a sourc=
e of
bugs.=