From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11326] New: sysvinit fails to build in latest GIT master
Date: Tue, 11 Sep 2018 08:40:18 +0000 [thread overview]
Message-ID: <bug-11326-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11326
Bug ID: 11326
Summary: sysvinit fails to build in latest GIT master
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: tpearson at raptorengineering.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7766
--> https://bugs.busybox.net/attachment.cgi?id=7766&action=edit
Add missing system macro include
sysvinit is missing the required macro #include to build on newer glibc
versions. OpenEmbedded has already patched this, buildroot should do the same.
Tested patch attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-09-11 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:40 bugzilla at busybox.net [this message]
2018-09-11 9:08 ` [Buildroot] [Bug 11326] sysvinit fails to build in latest GIT master bugzilla at busybox.net
2018-11-02 9:31 ` 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-11326-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.