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 13781] isc dhcp-server package don't create file /usr/bin/dhcpd
Date: Wed, 05 May 2021 19:23:40 +0000	[thread overview]
Message-ID: <bug-13781-163-mfxL5h4jph@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13781-163@https.bugs.busybox.net/>

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

--- Comment #4 from Arnout Vandecappelle <arnout@mind.be> ---
> Now i can't find the dhcpd-file in "build/target/usr/sbin/" or in the rootfs.tar. 
> In "build/build/dhcp-4.4.2/server" i found the file dhcpd

You did enable BR2_PACKAGE_DHCP_SERVER, right?

Which buildroot version are you using? There was a problem with installation
between Sat Apr 20 16:30:31 2019 and Thu Aug 1 18:26:09 2019 - if you happen to
use 2019.05 or 2019.05.1, you would have this problem.

I can't reproduce the issue here with your config file.

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

  parent reply	other threads:[~2021-05-05 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  7:46 [Buildroot] [Bug 13781] New: isc dhcp-server package don't create file /usr/bin/dhcpd bugzilla at busybox.net
2021-04-30  7:55 ` [Buildroot] [Bug 13781] " bugzilla at busybox.net
2021-04-30 20:12 ` bugzilla at busybox.net
2021-05-05 11:53 ` bugzilla at busybox.net
2021-05-05 19:23 ` bugzilla at busybox.net [this message]
2021-05-06  8:22 ` bugzilla at busybox.net
2021-05-06 12:59 ` bugzilla at busybox.net
2021-05-06 14:56 ` bugzilla at busybox.net
2021-05-06 16:03 ` bugzilla at busybox.net
2021-05-07  8:37 ` bugzilla at busybox.net
2021-05-07  9:59 ` 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-13781-163-mfxL5h4jph@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