Re: sed in CURRENT fails in textproc/jq

From: Antoine Brodin <antoine_at_freebsd.org>
Date: Sat, 09 Sep 2023 07:01:56 UTC 
On Sat, Sep 9, 2023 at 6:47 AM Yuri <yuri@freebsd.org> wrote:
>
> 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
>
>
> See the log:
> https://pkg-status.freebsd.org/beefy18/data/main-amd64-default/peb032111a352_s9c80d66ec1/logs/jq-1.7.log

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:
https://pkg-status.freebsd.org/gohan03/data/main-amd64-default-baseline/peb032111a352_s9c80d66ec1/logs/errors/readline-8.2.1.log
https://pkg-status.freebsd.org/gohan03/data/main-amd64-default-baseline/peb032111a352_s9c80d66ec1/logs/errors/expat-2.5.0.log
https://pkg-status.freebsd.org/gohan03/data/main-amd64-default-baseline/peb032111a352_s9c80d66ec1/logs/errors/libedit-3.1.20221030,1.log
etc.

Antoine