Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12051] New: Build succeeds but leaves a temporary libtool wrapper script for dhcp in the rootfs
Date: Mon, 22 Jul 2019 21:01:17 +0000	[thread overview]
Message-ID: <bug-12051-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 12051
              Host: i386
             Build: amd64
           Summary: Build succeeds but leaves a temporary libtool wrapper
                    script for dhcp in the rootfs
           Product: buildroot
           Version: 2019.05.1
          Hardware: All
                OS: Linux
            Status: NEW
          Keywords: link-failure
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: jakobcornell at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

It's all in the title. Make proceeds to completion, but the dhcp build doesn't
finish.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-07-22 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 21:01 bugzilla at busybox.net [this message]
2019-07-22 21:03 ` [Buildroot] [Bug 12051] Build succeeds but leaves a temporary libtool wrapper script for dhcp in the rootfs bugzilla at busybox.net
2019-07-22 21:07 ` bugzilla at busybox.net
2019-07-24  1:19 ` bugzilla at busybox.net
2019-07-24  1:23 ` [Buildroot] [Bug 12051] package/dhcp installs libtool wrapper scripts on target instead of real binaries bugzilla at busybox.net
2019-07-24  1:25 ` bugzilla at busybox.net
2019-07-24 16:53 ` bugzilla at busybox.net
2019-08-01 16:27 ` bugzilla at busybox.net

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-12051-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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