From: Rico Bachmann <bachmann@tofwerk.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] libfcgi: fix build with C++ support and gcc >= 4.4
Date: Tue, 01 May 2012 10:41:36 +0200 [thread overview]
Message-ID: <op.wdmfrmfg705kjs@rico> (raw)
In-Reply-To: 20120430193954.02DA196C2A@busybox.osuosl.org
Am 30.04.2012, 21:38 Uhr, schrieb Peter Korsgaard
<jacmet@sunsite.dk>:
> commit:
> http://git.buildroot.net/buildroot/commit/?id=ae63ca8f4782b91fd9e41316bfb79a43f54f5cd2
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> As reported on the ml by Rico Bachmann.
>
> Signed-off-by: Peter Korsgaard
> <jacmet@sunsite.dk>
> ---
> package/libfcgi/libfcgi-eof.patch | 24 ++++++++++++++++++++++++
> 1 files changed, 24 insertions(+), 0 deletions(-)
>
> diff --git a/package/libfcgi/libfcgi-eof.patch
> b/package/libfcgi/libfcgi-eof.patch
> new file mode 100644
> index 0000000..e731426
> --- /dev/null
> +++ b/package/libfcgi/libfcgi-eof.patch
> @@ -0,0 +1,24 @@
> +[PATCH] fix build with C++ support and gcc >= 4.4
> +
> +EOF is defined in stdio, so ensure it is included.
> +
> +Based on similar patch by Markus Rothe:
> +http://comments.gmane.org/gmane.comp.web.fastcgi.devel/3205
> +
> +Signed-off-by: Peter Korsgaard
> <jacmet@sunsite.dk>
> +---
> + libfcgi/fcgio.cpp | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +Index: fcgi-2.4.0/libfcgi/fcgio.cpp
> +===================================================================
> +--- fcgi-2.4.0.orig/libfcgi/fcgio.cpp
> ++++ fcgi-2.4.0/libfcgi/fcgio.cpp
> +@@ -22,6 +22,7 @@
> + #define DLLAPI __declspec(dllexport)
> + #endif
> +
> ++#include <cstdio>
> + #include <limits.h>
> + #include "fcgio.h"
Thanks for adding the patch.
I've just want to do it right now.
prev parent reply other threads:[~2012-05-01 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 19:38 [Buildroot] [git commit] libfcgi: fix build with C++ support and gcc >= 4.4 Peter Korsgaard
2012-05-01 8:41 ` Rico Bachmann [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=op.wdmfrmfg705kjs@rico \
--to=bachmann@tofwerk.com \
--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