Date: Sat, 09 Sep 2023 19:12:29 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Antoine Brodin <antoine@freebsd.org> Cc: Yuri <yuri@freebsd.org>, current <current@freebsd.org>, Robert Clausecker <fuz@FreeBSD.org> Subject: Re: sed in CURRENT fails in textproc/jq Message-ID: <86edj7qnia.fsf@ltc.des.no> In-Reply-To: <CAALwa8kAaDw80h2cbaeLOmw2G9EpRo6dJFZcFFc99mAU_7xkRA@mail.gmail.com> (Antoine Brodin's message of "Sat, 9 Sep 2023 07:01:56 %2B0000") References: <30a59ac0-28fd-f6ed-505c-9ef6d8e84fc3@tsoft.com> <CAALwa8kAaDw80h2cbaeLOmw2G9EpRo6dJFZcFFc99mAU_7xkRA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86edj7qnia.fsf>