From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Cc: Pieter De Gendt <pieter.degendt@gmail.com>
Subject: [Buildroot] [PATCH 2/2] package/libvips: bump version to 8.18.0
Date: Sat, 7 Mar 2026 20:08:51 +0100 [thread overview]
Message-ID: <20260307190851.853162-2-bernd@kuhls.net> (raw)
In-Reply-To: <20260307190851.853162-1-bernd@kuhls.net>
https://github.com/libvips/libvips/blob/v8.18.0/ChangeLog
Added dependency to gcc >= 4.9 due to C++14 features being used since
this version bump:
https://github.com/libvips/libvips/commit/3fa537480dda6170c3d8fb39abb838161d1c45ce
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
package/libvips/Config.in | 5 +++--
package/libvips/libvips.hash | 5 +++--
package/libvips/libvips.mk | 2 +-
3 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/package/libvips/Config.in b/package/libvips/Config.in
index 70d01f0e35..ec2d031141 100644
--- a/package/libvips/Config.in
+++ b/package/libvips/Config.in
@@ -2,6 +2,7 @@ config BR2_PACKAGE_LIBVIPS
bool "libvips"
depends on BR2_USE_WCHAR # libglib2
depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2
+ depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # C++14
depends on BR2_USE_MMU # fork()
# C++ support is required to build libvips
# https://github.com/jcupitt/libvips/issues/231
@@ -15,7 +16,7 @@ config BR2_PACKAGE_LIBVIPS
http://www.vips.ecs.soton.ac.uk/
-comment "libvips needs a toolchain w/ wchar, threads, C++"
+comment "libvips needs a toolchain w/ wchar, threads, C++, gcc >= 4.9"
depends on BR2_USE_MMU
depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || \
- !BR2_INSTALL_LIBSTDCPP
+ !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
diff --git a/package/libvips/libvips.hash b/package/libvips/libvips.hash
index dd7510ecb2..956ff5924a 100644
--- a/package/libvips/libvips.hash
+++ b/package/libvips/libvips.hash
@@ -1,3 +1,4 @@
-# From https://github.com/libvips/libvips/releases/download/v8.17.2/vips-8.17.2.tar.xz.sha256sum
-sha256 57ea0ec4f30ea04748c9e8eec5415e7c9ac7cafe6822e4788fc110376a1d224a vips-8.17.2.tar.xz
+# From https://github.com/libvips/libvips/releases/download/v8.18.0/vips-8.18.0.tar.xz.sha256sum
+sha256 b85ab92280c30d22f5c8fe2f68b809cddb7eaac437d8c33474475dac84ddc574 vips-8.18.0.tar.xz
+# Locally computed
sha256 dc626520dcd53a22f727af3ee42c770e56c97a64fe3adb063799d8ab032fe551 LICENSE
diff --git a/package/libvips/libvips.mk b/package/libvips/libvips.mk
index 729d5fb9e3..8e576038e7 100644
--- a/package/libvips/libvips.mk
+++ b/package/libvips/libvips.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBVIPS_VERSION = 8.17.2
+LIBVIPS_VERSION = 8.18.0
LIBVIPS_SOURCE = vips-$(LIBVIPS_VERSION).tar.xz
LIBVIPS_SITE = https://github.com/libvips/libvips/releases/download/v$(LIBVIPS_VERSION)
LIBVIPS_LICENSE = LGPL-2.1+
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-07 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 19:08 [Buildroot] [PATCH 1/2] package/libvips: fix static build Bernd Kuhls
2026-03-07 19:08 ` Bernd Kuhls [this message]
2026-03-07 20:12 ` Julien Olivain via buildroot
2026-03-14 7:54 ` Thomas Perale via buildroot
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=20260307190851.853162-2-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=pieter.degendt@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