From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 11 Apr 2023 08:25:01 +0200 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pm7R7-00HFxS-0L for lore@lore.pengutronix.de; Tue, 11 Apr 2023 08:25:01 +0200 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1pm7R7-0002ym-CC; Tue, 11 Apr 2023 08:25:01 +0200 Received: from pty.hi.pengutronix.de ([2001:67c:670:100:1d::c5]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pm7QY-0002yd-EN; Tue, 11 Apr 2023 08:24:26 +0200 Received: from rsc by pty.hi.pengutronix.de with local (Exim 4.94.2) (envelope-from ) id 1pm7QX-009LLp-Qr; Tue, 11 Apr 2023 08:24:25 +0200 Date: Tue, 11 Apr 2023 08:24:25 +0200 From: Robert Schwebel To: ptxdist@pengutronix.de, christian.melki@t2data.com Message-ID: References: <20230404080026.4490-1-r.schwebel@pengutronix.de> <1d7f8e93-9949-8ef2-8c53-5d8aac586bd5@t2data.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d7f8e93-9949-8ef2-8c53-5d8aac586bd5@t2data.com> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-Accept-Language: de,en X-Accept-Content-Type: text/plain Subject: Re: [ptxdist] [PATCH] openssl: add dependency to libatomic X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false On Sat, Apr 08, 2023 at 10:57:44PM +0200, Christian Melki wrote: > >>> Hmm, with ptxdist-2023.04.0, I don't get the corresponding error any > >>> more (and instead a reason warning that libatomic is unused). Let's drop > >>> this for now. > >> > >> atomic is going to be highly dependent on toolchain, arch etc. > >> unless you're going to be more specific I suspect complains will happen > >> in both directions. > > > > True - now with the change removed, I see the issue on MIPS. Our > > "reason" checker now claims that /usr/lib/libcrypto.so.3 depends on > > libatomic.so.1 which is not there. v7a and v8a and x86_64 seem to be > > happy without it. > > > >> I'd be more interested why and where this pops up than adding a > >> blanket _ATOMIC. Ie. I agree on the drop. :) > > > > I'm a bit unsure what to do now :) > > Toolchain versions? Same as before: OSELAS.Toolchain-2022.10.0/mips-softfloat-linux-gnu/gcc-12.2.1-glibc-2.36-binutils-2.39-kernel-6.0.5-sanitized > What mips are we talking about? See above, mips-softfloat-linux-gnu. > If a sufficiently modern gcc doesn't provide a complete set of > intrinsics for atomics then libatomic is going to be the only choice. At least some configure scripts report "checking for lock-free atomic intrinsics... yes" > Can you figure out what symbols would be attached to libatomic? rsc@dude05:~/work/DistroKit$ selected_toolchain/mips-softfloat-linux-gnu-nm -n platform-mips/packages/openssl-3.1.0/usr/lib/libcrypto.so.3 | grep LIBATOMIC U __atomic_fetch_or_8@LIBATOMIC_1.0 U __atomic_is_lock_free@LIBATOMIC_1.0 U __atomic_load_8@LIBATOMIC_1.0 > I'm suspecting that if you have an older gcc(?) some intrinsics might > not be available. rsc -- Pengutronix e.K. | Dipl.-Ing. Robert Schwebel | Steuerwalder Str. 21 | https://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |