From: Bartosz Golaszewski <brgl@bgdev.pl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] doxygen: fix a build issue
Date: Mon, 26 Jun 2017 11:20:13 +0200 [thread overview]
Message-ID: <1498468814-2179-1-git-send-email-brgl@bgdev.pl> (raw)
I have submitted this fix for upstream inclusion, but I don't know how
long it will take for the maintainers to respond. In the meantime I'm
still getting these build reports everyday on my e-mail.
This patch fixes the doxygen build issues by fixing a script generating
a C header file. The script redirects its stderr to the generated file
so any warning emitted by it or its child processes ends up in this
very file. This is obviously broken and needs to be changed.
Bartosz Golaszewski (1):
doxygen: fix a build issue
...build-fix-the-way-lang_cfg.h-is-generated.patch | 58 ++++++++++++++++++++++
1 file changed, 58 insertions(+)
create mode 100644 package/doxygen/0002-build-fix-the-way-lang_cfg.h-is-generated.patch
--
2.9.3
next reply other threads:[~2017-06-26 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 9:20 Bartosz Golaszewski [this message]
2017-06-26 9:20 ` [Buildroot] [PATCH] doxygen: fix a build issue Bartosz Golaszewski
2017-07-02 16:38 ` Peter Korsgaard
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=1498468814-2179-1-git-send-email-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--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