mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de, christian.melki@t2data.com
Subject: Re: [ptxdist] [PATCH] openssl: add dependency to libatomic
Date: Sat, 8 Apr 2023 22:30:58 +0200	[thread overview]
Message-ID: <ZDHPAgq9tAT8H31P@pengutronix.de> (raw)
In-Reply-To: <ce329951-f1f8-bf53-6f61-766f839a29fd@t2data.com>

On Sat, Apr 08, 2023 at 03:20:25PM +0200, Christian Melki wrote:
> On 4/8/23 15:08, Robert Schwebel wrote:
> > On Tue, Apr 04, 2023 at 10:00:26AM +0200, Robert Schwebel wrote:
> >> Since openssl 3.x, libcrypto needs libatomic, at least on several 32 bit
> >> platforms (and on 64 bit it doesn't harm).
> >>
> >> Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
> >> ---
> >>  rules/openssl.in | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/rules/openssl.in b/rules/openssl.in
> >> index 629ee3057..a86ca66a2 100644
> >> --- a/rules/openssl.in
> >> +++ b/rules/openssl.in
> >> @@ -4,6 +4,7 @@ menuconfig OPENSSL
> >>  	tristate
> >>  	select LIBC_DL
> >>  	select GCCLIBS_GCC_S
> >> +	select GCCLIBS_ATOMIC
> >>  	select CRYPTODEV_API		if OPENSSL_CRYPTODEV && BUILDTIME
> >>  	prompt "openssl                       "
> >>  	help
> > 
> > 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 :)

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    |



  reply	other threads:[~2023-04-08 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04  8:00 Robert Schwebel
2023-04-08 13:08 ` Robert Schwebel
2023-04-08 13:20   ` Christian Melki
2023-04-08 20:30     ` Robert Schwebel [this message]
2023-04-08 20:57       ` Christian Melki
2023-04-11  6:24         ` Robert Schwebel
2023-04-11  6:47           ` Christian Melki

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=ZDHPAgq9tAT8H31P@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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