From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/3] package/spandsp: bump version
Date: Tue, 3 Feb 2026 23:10:16 +0100 [thread overview]
Message-ID: <aYJw2tcO9_Rmx8OM@windsurf> (raw)
In-Reply-To: <20260103094508.1212757-3-bernd@kuhls.net>
Hello Bernd,
On Sat, Jan 03, 2026 at 10:45:08AM +0100, Bernd Kuhls wrote:
> Removed patch which is included in this release.
>
> Switched to github helper to download the current git tree instead of
> using outdated tarball snapshots.
>
> The currently used tarball contains the git tree as of 2020-08-14:
> https://github.com/freeswitch/spandsp/commit/6ec23e5a7e411a22d59e5678d12c4d2942c4a4b6
>
> The newest tarball provided by upstream
> https://files.freeswitch.org/downloads/libs/spandsp-3.0.0-0d2e6ac65e.tar.gz
> contains the git tree as of 2023-06-16:
> https://github.com/freeswitch/spandsp/tree/0d2e6ac65e0e8f53d652665a743015a88bf048d4
>
> and lacks the fix for gcc-14.x added to buildroot in patch 0002.
>
> Build-tested using this defconfig:
>
> BR2_x86_64=y
> BR2_x86_corei7=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_X86_64_CORE_I7_GLIBC_BLEEDING_EDGE=y
> BR2_PER_PACKAGE_DIRECTORIES=y
> BR2_INIT_NONE=y
> BR2_PACKAGE_BLUEZ_ALSA=y
> BR2_PACKAGE_FREESWITCH=y
> BR2_PACKAGE_WIRESHARK=y
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Unfortunately, this patch seems to break the build for me:
In file included from ../src/make_v34_probe_signals.c:28:
../src/spandsp.h:48:10: fatal error: tiffio.h: No such file or directory
48 | #include <tiffio.h>
| ^~~~~~~~~~
compilation terminated.
Reproduced with:
BR2_aarch64=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_AARCH64_GLIBC_STABLE=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_SPANDSP=y
# BR2_TARGET_ROOTFS_TAR is not set
Could you have a look?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-03 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 9:45 [Buildroot] [PATCH 1/3] package/spandsp: fix build with gcc-14.x Bernd Kuhls
2026-01-03 9:45 ` [Buildroot] [PATCH 2/3] package/freeswitch: Fix compilation against >=2023/06/02 spandsp Bernd Kuhls
2026-02-03 22:10 ` Thomas Petazzoni via buildroot
2026-01-03 9:45 ` [Buildroot] [PATCH 3/3] package/spandsp: bump version Bernd Kuhls
2026-02-03 22:10 ` Thomas Petazzoni via buildroot [this message]
2026-02-03 21:41 ` [Buildroot] [PATCH 1/3] package/spandsp: fix build with gcc-14.x Thomas Petazzoni via buildroot
2026-02-13 19:37 ` 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=aYJw2tcO9_Rmx8OM@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.