From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/kodi: fix build with newer gcc versions.
Date: Sun, 16 Jul 2017 09:58:34 +0200 [thread overview]
Message-ID: <20170716095834.38eaee7a@windsurf> (raw)
In-Reply-To: <20170715141419.13160-1-bernd.kuhls@t-online.de>
Hello,
On Sat, 15 Jul 2017 16:14:19 +0200, Bernd Kuhls wrote:
> Using this defconfig produces a build error with kodi:
>
> BR2_arm=y
> BR2_cortex_a8=y
> BR2_ARM_INSTRUCTIONS_THUMB2=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_PACKAGE_KODI=y
> BR2_PACKAGE_SUNXI_MALI=y
> BR2_PACKAGE_PYTHON=y
> BR2_PACKAGE_PYTHON_PY_ONLY=y
>
> /home/buildroot/buildroot/output/build/kodi-17.3-Krypton/xbmc/filesystem/FTPParse.cpp:37:1:
> error: ?string? does not name a type
> string CFTPParse::getName()
> ^~~~~~
> /home/buildroot/buildroot/output/build/kodi-17.3-Krypton/xbmc/filesystem/FTPParse.cpp:62:25:
> error: variable or field ?setTime? declared void
> void CFTPParse::setTime(string str)
> ^~~~~~
> /home/buildroot/buildroot/output/build/kodi-17.3-Krypton/xbmc/filesystem/FTPParse.cpp:62:25:
> error: ?string? was not declared in this scope
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> .../kodi/0003-FTPParse.cpp-use-std-string.patch | 91 ++++++++++++++++++++++
> 1 file changed, 91 insertions(+)
> create mode 100644 package/kodi/0003-FTPParse.cpp-use-std-string.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-16 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 14:14 [Buildroot] [PATCH 1/1] package/kodi: fix build with newer gcc versions Bernd Kuhls
2017-07-16 7:58 ` 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=20170716095834.38eaee7a@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox