Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15396] New: Document build dependencies
Date: Tue, 14 Mar 2023 20:08:39 +0000	[thread overview]
Message-ID: <bug-15396-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 15396
           Summary: Document build dependencies
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: jbglaw@lug-owl.de
                CC: buildroot@uclibc.org
  Target Milestone: ---

Hi!

In an attempt to do CI builds for a number of projects, I started to also build
buildroot configurations (cf. http://toolchain.lug-owl.de/)  This generally
works quite well (at least as far as configurations have been attempted.)
However, I noticed that for some sample configs (at least true for the
`beaglebone_defconfig` and `grinn_chiliboard_defconfig` configurations, maybe
others.) They both pull in `<openssl/evp.h>` via [uboot]/tools/aisimage.c ->
tools/imagetool.h -> include/image.h .

I suggest adding `libssl-dev` to the list of optional packages
(https://nightly.buildroot.org/manual.html#requirement-optional).

Thanks,
  Jan-Benedict

-- 
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:[~2023-03-14 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 20:08 bugzilla [this message]
2023-03-14 21:29 ` [Buildroot] [Bug 15396] Document build dependencies bugzilla
2023-03-14 21:37 ` 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@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