Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/assimp: fix musl zlib/zip related compile failure
Date: Fri, 10 Apr 2020 22:46:11 +0200	[thread overview]
Message-ID: <20200410224611.1db11073@windsurf.home> (raw)
In-Reply-To: <20200410163237.30240-1-ps.report@gmx.net>

On Fri, 10 Apr 2020 18:32:37 +0200
Peter Seiderer <ps.report@gmx.net> wrote:

> As assimp fails to use system provided zlib/zip (and is picky
> about the provided versions) use assimp contributed one
> and backport one part of upstream patch to fix musl compile.
> 
> Fixes:
> 
>   http://autobuild.buildroot.net/results/4b373ae7d8fd40efe3e2592f94f2d769d6a77669
> 
>   In file included from .../assimp-5.0.1/code/3MF/D3MFExporter.cpp:61:
>   .../assimp-5.0.1/contrib/zip/src/zip.h:30:15: error: conflicting declaration 'typedef long int ssize_t'
>    typedef long  ssize_t;  /* byte count or error */
>                  ^~~~~~~
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  ...ssize_t-typedef-mismatch-for-musl-co.patch | 50 +++++++++++++++++++
>  package/assimp/Config.in                      |  1 -
>  package/assimp/assimp.mk                      |  3 +-
>  3 files changed, 51 insertions(+), 3 deletions(-)
>  create mode 100644 package/assimp/0002-contrib-zip-fix-ssize_t-typedef-mismatch-for-musl-co.patch

I've applied, but it's not really great to be forced to use the
internal zlib. Could you try to work this out with upstream?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-04-10 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 16:32 [Buildroot] [PATCH v1] package/assimp: fix musl zlib/zip related compile failure Peter Seiderer
2020-04-10 20:46 ` Thomas Petazzoni [this message]
2020-04-11 13:01   ` Peter Seiderer

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=20200410224611.1db11073@windsurf.home \
    --to=thomas.petazzoni@bootlin.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