From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15396] Document build dependencies
Date: Tue, 14 Mar 2023 21:29:31 +0000 [thread overview]
Message-ID: <bug-15396-163-g7r9iIPAwN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15396-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15396
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Thanks for the reporting the issue. However, the correct fix is not to add
libssl-dev as a dependency of Buildroot. Instead if U-Boot needs OpenSSL on the
host, the Buildroot option BR2_TARGET_UBOOT_NEEDS_OPENSSL should be enabled.
Could you try adding BR2_TARGET_UBOOT_NEEDS_OPENSSL=y in the problematic
defconfigs? This should address your problem.
We normally also have CI to test all our defconfigs within a clean container,
but our pipelines are so long that Gitlab CI is regularly aborting them in the
middle, making said CI pretty useless unfortunately :-/
--
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
next prev parent reply other threads:[~2023-03-14 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 20:08 [Buildroot] [Bug 15396] New: Document build dependencies bugzilla
2023-03-14 21:29 ` bugzilla [this message]
2023-03-14 21:37 ` [Buildroot] [Bug 15396] " bugzilla
2023-03-15 20:56 ` bugzilla
2023-03-16 10:49 ` bugzilla
2023-04-03 13:25 ` bugzilla
2023-04-04 16:37 ` bugzilla
2024-06-15 15:06 ` 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-15396-163-g7r9iIPAwN@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