Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15591] New: zerofree: missing library and allow static build
Date: Mon, 22 May 2023 11:31:56 +0000	[thread overview]
Message-ID: <bug-15591-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 15591
           Summary: zerofree: missing library and allow static build
           Product: buildroot
           Version: 2023.02.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: andrea.biardi@viavisolutions.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Created attachment 9596
  --> https://bugs.busybox.net/attachment.cgi?id=9596&action=edit
proposed patch

Two minor problems with the recently-added zerofree target package:

- It needs to be linked with "com_err".
- The Config.in file says it "needs a toolchain w/ dynamic library", but that
doesn't seem to be the case, as it builds and works perfectly when statically
linked (at least with musl, probably with uclibc as well).

Patch attached for consideration.

-- 
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-05-22 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 11:31 bugzilla [this message]
2024-06-15 15:10 ` [Buildroot] [Bug 15591] zerofree: missing library and allow static build 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-15591-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