From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libheif: fix libjpeg build
Date: Mon, 18 Mar 2024 14:25:27 +0100 [thread overview]
Message-ID: <87y1affz94.fsf@48ers.dk> (raw)
In-Reply-To: <20240228174721.1141838-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Wed, 28 Feb 2024 18:47:21 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> libheif raises the following build failure with libjpeg since bump to
> version 1.17.5 in commit 5714126edac88e3adc043a482b262b319a907dd3 and
> https://github.com/strukturag/libheif/commit/ebd13a20b8b7f1964939642b08b662ef7e483f39
> /home/buildroot/autobuild/instance-3/output-1/build/libheif-1.17.5/libheif/plugins/encoder_jpeg.cc:
> In function 'heif_error jpeg_encode_image(void*, const heif_image*,
> heif_image_input_class)':
> /home/buildroot/autobuild/instance-3/output-1/build/libheif-1.17.5/libheif/plugins/encoder_jpeg.cc:366:37:
> error: invalid conversion from 'long unsigned int*' to 'size_t*' {aka
> 'unsigned int*'} [-fpermissive]
> 366 | jpeg_mem_dest(&cinfo, &outbuffer, &outlength);
> | ^~~~~~~~~~
> | |
> | long unsigned int*
> Fixes:
> - http://autobuild.buildroot.org/results/8ca909564c8dabe28ad08c96ebbc04b25592e727
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-03-18 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 17:47 [Buildroot] [PATCH 1/1] package/libheif: fix libjpeg build Fabrice Fontaine
2024-02-29 16:07 ` Peter Korsgaard
2024-03-18 13:25 ` Peter Korsgaard [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=87y1affz94.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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