All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] fbterm: fix musl compile
Date: Sat, 10 Oct 2015 11:38:15 +0200	[thread overview]
Message-ID: <20151010113815.2ee9d030@free-electrons.com> (raw)
In-Reply-To: <1444329302-13716-1-git-send-email-ps.report@gmx.net>

Dear Peter Seiderer,

On Thu,  8 Oct 2015 20:35:02 +0200, Peter Seiderer wrote:
> - add missing include, fixes:
> 
>   fbio.cpp:33:8: error: ?fd_set? does not name a type
>    static fd_set fds;
> 
>   improxy.cpp:439:3: error: ?fd_set? was not declared in this scope
> 
> - add missing WAIT_ANY define, fixes:
> 
>   fbterm.cpp: In member function ?void FbTerm::processSignal(u32)?:
>   fbterm.cpp:212:22: error: ?WAIT_ANY? was not declared in this scope
>       s32 pid = waitpid(WAIT_ANY, 0, WNOHANG);
> 
> Fixes:
> http://autobuild.buildroot.net/results/ab2/ab2334700b44bac233994b76f2acf1795f0
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  ...p-improxy.cpp-fbterm.cpp-fix-musl-compile.patch | 70 ++++++++++++++++++++++
>  1 file changed, 70 insertions(+)
>  create mode 100644 package/fbterm/0001-fbio.cpp-improxy.cpp-fbterm.cpp-fix-musl-compile.patch

Applied, thanks. However, this project is still hosted on Google Code,
and has not seen any release since 2010. Not nice since it means we
cannot upstream the patch :-/

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-10-10  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 18:35 [Buildroot] [PATCH v1] fbterm: fix musl compile Peter Seiderer
2015-10-10  9:38 ` Thomas Petazzoni [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=20151010113815.2ee9d030@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 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.