All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Gregory Dymarek <gregd72002@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/sofia-sip: needs OpenSSL
Date: Thu, 17 Sep 2026 08:37:12 +0200	[thread overview]
Message-ID: <aquKZTaCLuEQfmEZ@windsurf> (raw)
In-Reply-To: <20260917000152.3060291-1-bernd@kuhls.net>

On Thu, Sep 17, 2026 at 02:01:52AM +0200, Bernd Kuhls wrote:
> Buildroot commit bb254e2304274dc308e3d8699e92ea77e4189fb7 bumped the
> package to version 1.13.18 which includes upstream commit
> https://github.com/freeswitch/sofia-sip/commit/8081a1a6d05f174cb902664f73182c32fd2eee0f
> that added the unconditional usage of OpenSSL.
> 
> Tested with both LibreSSL and OpenSSL, the latter with all suboptions
> disabled.
> 
> Fixes:
> https://autobuild.buildroot.net/results/afe/afe7b327f12db86e4dc31ecc25b576bff5c4a0bb/
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to master, thanks! However, could you submit a bug report
upstream? Indeed, it is not normal for the build to blow up: the lack
of OpenSSL should be detected at the configure.ac level. This bug
report will also allow to check whether making OpenSSL a mandatory
dependency is really a conscious decision from the upstream
maintainers.

Thanks a lot!

Thomas Petazzoni
-- 
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:[~2026-09-17  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  0:01 [Buildroot] [PATCH 1/1] package/sofia-sip: needs OpenSSL Bernd Kuhls
2026-09-17  6:37 ` Thomas Petazzoni via buildroot [this message]
2026-09-25 14:46 ` Raphaël Mélotte via buildroot

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=aquKZTaCLuEQfmEZ@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=gregd72002@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.