All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2, 1/1] utils/genrandconfig: disable libopenssl without atomics
Date: Thu, 11 Aug 2022 22:55:04 +0200	[thread overview]
Message-ID: <20220811225504.1e00963e@windsurf> (raw)
In-Reply-To: <CAPi7W83tLTuFGd6MB2uLDip5fhmEkFZx7xQOzaJ5qNaOKPF4Xw@mail.gmail.com>

On Wed, 10 Aug 2022 23:17:01 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Indeed, but libatomic is not available/enabled on all those autobuilder
> build failures.
> For example, BR2_TOOLCHAIN_HAS_LIBATOMIC can't be found in
> http://autobuild.buildroot.org/results/bce526d538f43a541fdfbc0c9b4a7cecebbbc539/config

Gah, indeed, configurations without threads, or with FLAT binaries
don't have libatomic. And indeed, propagating this dependency to all
reverse dependencies of openssl seems like a nightmare...

On the other hand, openssl is really a base library, one could see it
being enabled on a noMMU system. So real users could encounter this
build issue, if we simply avoid the problem at the autobuilder level.

I don't really have a clever idea here :-/

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-08-11 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 16:27 [Buildroot] [PATCH v2, 1/1] utils/genrandconfig: disable libopenssl without atomics Fabrice Fontaine
2022-08-10 21:07 ` Thomas Petazzoni via buildroot
2022-08-10 21:17   ` Fabrice Fontaine
2022-08-11 20:55     ` Thomas Petazzoni via buildroot [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=20220811225504.1e00963e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.