Date: Sun, 10 Sep 2023 06:51:09 +0200 From: Robert Clausecker <fuz@fuz.su> To: current@freebsd.org Subject: Re: sed in CURRENT fails in textproc/jq Message-ID: <ZP1LPZcC99zIS1Jp@fuz.su> In-Reply-To: <86edj7qnia.fsf@ltc.des.no> References: <30a59ac0-28fd-f6ed-505c-9ef6d8e84fc3@tsoft.com> <CAALwa8kAaDw80h2cbaeLOmw2G9EpRo6dJFZcFFc99mAU_7xkRA@mail.gmail.com> <86edj7qnia.fsf@ltc.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZP1LPZcC99zIS1Jp>