From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] assimp: fix bfin compile
Date: Sat, 16 Jan 2016 14:07:35 +0100 [thread overview]
Message-ID: <20160116140735.32b862b5@free-electrons.com> (raw)
In-Reply-To: <1452807861-1020-1-git-send-email-ps.report@gmx.net>
Dear Peter Seiderer,
On Thu, 14 Jan 2016 22:44:20 +0100, Peter Seiderer wrote:
> Use proper 64-bit constant for CONVERT_FBX_TIME(time) conversion.
>
> Fixes ([1]):
>
> code/FBXConverter.cpp:2025: error: integer constant is too large for 'long' type
> code/FBXConverter.cpp:2026: error: integer constant is too large for 'long' type
> code/FBXConverter.cpp:2794: error: integer constant is too large for 'long' type
> code/FBXConverter.cpp:2868: error: integer constant is too large for 'long' type
> code/FBXConverter.cpp:2878: error: integer constant is too large for 'long' type
> code/FBXConverter.cpp:2888: error: integer constant is too large for 'long' type
>
> [1] http://autobuild.buildroot.net/results/885/8853b192d16ca7ef769c5352a2df0540a7a2a4fd
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> ...x-FBXConverter-use-proper-64-bit-constant.patch | 35 ++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 package/assimp/0001-Fix-FBXConverter-use-proper-64-bit-constant.patch
Both patches applied, thanks! For the first patch, please make sure to
submit it upstream.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-01-16 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:44 [Buildroot] [PATCH v1 1/2] assimp: fix bfin compile Peter Seiderer
2016-01-14 21:44 ` [Buildroot] [PATCH v1 2/2] assimp: fix compile for big endian target Peter Seiderer
2016-01-16 13:07 ` 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=20160116140735.32b862b5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox