Re: sed in CURRENT fails in textproc/jq

Greetings,

I apologise for the inconvenience.  The issue seems to boil down to
various places calling

    memchr(buf, c, SIZE_MAX);

which causes an overflow when my newly written memchr() computes buf +
len to find the end of the buffer.  A patch to alleviate this issue can
be found here:

    http://fuz.su/~fuz/freebsd/0001-lib-libc-amd64-string-memchr.S-fix-behaviour-with-ov.patch

Please check if it does the trick for you.  If yes, I'll go ahead and
push it tomorrow-ish.

Yours,
Robert Clausecker

Am Sat, Sep 09, 2023 at 07:12:29PM +0200 schrieb Dag-Erling Smørgrav:
> Antoine Brodin <antoine@freebsd.org> writes:
> > Yuri <yuri@freebsd.org> writes:
> > > Either something has changed in sed(1) in CURRENT, or sed just fails
> > > during the configure stage of textproc/jq:
> > >
> > > sed: No error: 0
> > > checking for sys/cygwin.h... eval: ${+...}: Bad substitution
> > This seems to be a recent issue (less than 5 days).
> > Hundreds of configure scripts now fail to run on 15-current due to
> > this sed failure: [...]
> 
> Try adding ARCHLEVEL=scalar to CONFIGURE_ENV on one of these.  If that
> helps, yell at fuz@ :)
> 
> DES
> -- 
> Dag-Erling Smørgrav - des@FreeBSD.org
> 

-- 
()  ascii ribbon campaign - for an 8-bit clean world 
/\  - against html email  - against proprietary attachments