From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15396] Document build dependencies
Date: Tue, 14 Mar 2023 21:37:24 +0000 [thread overview]
Message-ID: <bug-15396-163-qVKire2zDI@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 #2 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
Once the current round of builds (about 2300 jobs, takes a few days) is done,
I'll happily test adding BR2_TARGET_UBOOT_NEEDS_OPENSSL=y to those configs and
re-run them with a container that doesn't have libssl-dev installed.
(As I realized this possible dependency, I added libssl-dev to the container,
not thinking about adding the dep'cy to the config. So this run won't catch
other configurations in need of BR2_TARGET_UBOOT_NEEDS_OPENSSL=y, but the next
round will catch that.)
As for CI builds, I cannot do daily builds (scheduling isn't an issue, but I
don't have the computation power), but if it's going to be helpful, I'll keep
buildroot builds every now and then. Will probably come out as one (full) build
every three to four weeks.
--
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:37 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 ` [Buildroot] [Bug 15396] " bugzilla
2023-03-14 21:37 ` bugzilla [this message]
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-qVKire2zDI@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