Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16114] New: dovecot 2.3.21 fails to build on 2024.05 with gcc-14 + musl + opensll
Date: Mon, 24 Jun 2024 08:30:21 +0000	[thread overview]
Message-ID: <bug-16114-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=16114

            Bug ID: 16114
           Summary: dovecot 2.3.21 fails to build on  2024.05 with gcc-14
                    + musl  + opensll
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: wutoiayr@pokemail.net
                CC: buildroot@uclibc.org
  Target Milestone: ---

Created attachment 9757
  --> https://bugs.busybox.net/attachment.cgi?id=9757&action=edit
build log

On 2024.05 with the attached config dovecot fails to build with openssl.

Probably dovecot needs to select BR2_PACKAGE_LIBOPENSSL_ENGINES when choosing
LIBOPENSS.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-06-24  8:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24  8:30 bugzilla [this message]
2024-06-24  8:49 ` [Buildroot] [Bug 16114] dovecot 2.3.21 fails to build on 2024.05 with gcc-14 + musl + opensll bugzilla

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=bug-16114-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox