From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8ED423858D33; Thu, 9 Mar 2023 11:28:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8ED423858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678361280; bh=ScnKMFhEIgi1THM3wbtPrBSBocwof556qjk7OVcblr4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=V0M18VWUkwlbIYWe37TyM1MKHatm2VJsUhG2uU36DGJeKWbRoOQ7u8KbiYrcr6/ZO yWi5Qh2Yjk0qAt+Lwz/PVc3OxK4XrsmCLw+kbQX/vDvajMqh+rtT/iXjHVOsPCJhZY Lp5AN14+mT6WaBZwwQCI6PiMRv7Y+Q+afE+VRQ6g= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109074] SIGABRT signal without using -lpthread at Linux RHEL 7.3 Date: Thu, 09 Mar 2023 11:28:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.8.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109074 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|MOVED |INVALID --- Comment #2 from Andrew Pinski --- Actually there is no bug here. With older versions of glibc, you need to li= nk against libpthread to get threads in general. This is true with any version= of gcc.=