All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 1/1] package/opensc: link with -latomic if needed
Date: Mon, 24 Jul 2023 22:48:17 +0200	[thread overview]
Message-ID: <pan$22ac9$82d21647$d8e54d59$6b8e9f97@ID-313208.user.individual.net> (raw)
In-Reply-To: 20230720231717.33ed6806__30743.4139352821$1689887867$gmane$org@windsurf

Am Thu, 20 Jul 2023 23:17:17 +0200 schrieb Thomas Petazzoni via buildroot:

> I continue to think this is not the right way of handling this issue.
> opensc is using pkg-config to detect openssl, so it is the openssl .pc
> files that should have -latomic. This will fix the issue once for all
> for all users of openssl, without chasing them down one by one.

Hi Thomas,

openssl has everything in place for statically linking to libatomic:

cat output/per-package/opensc/host/arceb-buildroot-linux-uclibc/sysroot/
usr/lib/pkgconfig/libcrypto.pc | grep atomic

Libs.private: -ldl -pthread -latomic -latomic

It's just the build system of opensc which does not make use of it. Due to 
my limited coding skills I only managed to disable building the test 
binaries which include the broken file:
https://patchwork.ozlabs.org/project/buildroot/patch/
20230724204439.1526127-1-bernd@kuhls.net/

Regards, Bernd

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-07-24 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 18:54 [Buildroot] [PATCH 1/1] package/opensc: link with -latomic if needed Bernd Kuhls
2023-07-20 21:17 ` Thomas Petazzoni via buildroot
     [not found] ` <20230720231717.33ed6806__30743.4139352821$1689887867$gmane$org@windsurf>
2023-07-24 20:48   ` Bernd Kuhls [this message]

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='pan$22ac9$82d21647$d8e54d59$6b8e9f97@ID-313208.user.individual.net' \
    --to=bernd@kuhls.net \
    --cc=buildroot@uclibc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.