On Sun, Feb 22, 2026 at 05:44:02PM +0100, Aurelien Jarno wrote:
> Hi,
> 
> On 2026-02-22 11:32, Thomas Dickey wrote:
> > On Sun, Feb 22, 2026 at 05:17:07PM +0100, Aurelien Jarno wrote:
> > > Source: rcs-blame
> > > Version: 1.4+20240206-1
> > 
> > that's old.  I've updated it a couple of times since that point.
> > 
> > 20251006 is "current"
> 
> Hmm, this still seems the newest available version:

sure - but I'm "upstream",
        - not a DD, and
        - would need a sponsor to do the work myself.  
 
> $ rmadison rcs-blame
> rcs-blame  | 1.3.1-4.2         | oldoldstable   | source, amd64, arm64, 
> armhf, i386
> rcs-blame  | 1.3.1-4.2         | oldstable      | source, amd64, arm64, 
> armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
> rcs-blame  | 1.4+20240206-1    | stable         | source, amd64, arm64, 
> armel, armhf, i386, ppc64el, riscv64, s390x
> rcs-blame  | 1.4+20240206-1    | testing        | source, amd64, armhf, i386, 
> ppc64el, riscv64, s390x
> rcs-blame  | 1.4+20240206-1    | unstable       | source, amd64, armhf, i386, 
> loong64, ppc64el, riscv64, s390x
> rcs-blame  | 1.4+20240206-1    | unstable-debug | source
> rcs-blame  | 1.4+20240206-1+b1 | testing        | arm64
> rcs-blame  | 1.4+20240206-1+b1 | unstable       | arm64
> 
> > > Severity: important
> > > Tags: ftbfs upstream
> > > Justification: fails to build from source
> > > User: [email protected]
> > > Usertags: glibc-2.43
> > > 
> > > Dear maintainer(s),
> > > 
> > > rcs-blame fails to build from source with glibc 2.43, currently in
> > > experimental. From the build log:
> > 
> > ...but I'm not tracking experimental (it would help if this report started
> > from 20251006)
> 
> Where is this packaged?
> 
> > > The full build log is available here [1].
> > > 
> > > The issue is due to ISO C23 declaration of bsearch, memchr, strchr,
> > > strpbrk, strrchr, strstr, wcschr, wcspbrk, wcsrchr, wcsstr and wmemchr,
> > > which now returns a pointer to a const-qualified type when the input
> > > argument is a pointer to a const-qualified type [2].
> > 
> > fwiw, I'd used gcc 15.2.1 in October.
> 
> This is not linked with GCC 15, but rather to a changed introduced in 
> glibc 2.43 to support this ISO C23 feature.

I understand (have seen some unnecessary breakage due to this feature)

-- 
Thomas E. Dickey <[email protected]>
https://invisible-island.net

Attachment: signature.asc
Description: PGP signature

Reply via email to