From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9216] log4cpp package build fails to build within install
Date: Mon, 12 Sep 2016 14:40:18 +0000 [thread overview]
Message-ID: <bug-9216-163-Z2Xafz34bJ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9216-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9216
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
This problem has already been fixed in commit
https://git.buildroot.org/buildroot/commit/package/log4cpp?id=bf20a49d4c2f064015b4d437a7cd98c6dd8ce4ff,
which is part of Buildroot since 2016.08. This commit disables the build of the
documentation, since Buildroot generally doesn't build the documentation of its
packages.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-09-12 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 6:08 [Buildroot] [Bug 9216] New: log4cpp package build fails to build within install bugzilla at busybox.net
2016-09-12 14:40 ` bugzilla at busybox.net [this message]
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-9216-163-Z2Xafz34bJ@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.