From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13506] New: BR2_PACKAGE_DHCPCD missing directory creation
Date: Sat, 30 Jan 2021 19:12:51 +0000 [thread overview]
Message-ID: <bug-13506-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13506
Bug ID: 13506
Summary: BR2_PACKAGE_DHCPCD missing directory creation
Product: buildroot
Version: 2020.11.1
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: miohna at freenet.de
CC: buildroot at uclibc.org
Target Milestone: ---
dhcpcd expects the directory /var/db/dhcpcd/ being present for the storage of
various files. However, this directory is not created during a default build
process of this package, causing error messages at run time.
Suggesting to add a mkdir -p /var/db/dhcpcd/ in file /package/dhcpcd/dhcpcd.mk
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-30 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 19:12 bugzilla at busybox.net [this message]
2021-02-02 17:13 ` [Buildroot] [Bug 13506] BR2_PACKAGE_DHCPCD missing directory creation bugzilla at busybox.net
2021-02-02 18:01 ` 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-13506-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.