Date: Sat, 9 Sep 2023 07:01:56 +0000 From: Antoine Brodin <antoine@freebsd.org> To: Yuri <yuri@freebsd.org> Cc: current <current@freebsd.org> Subject: Re: sed in CURRENT fails in textproc/jq Message-ID: <CAALwa8kAaDw80h2cbaeLOmw2G9EpRo6dJFZcFFc99mAU_7xkRA@mail.gmail.com> In-Reply-To: <30a59ac0-28fd-f6ed-505c-9ef6d8e84fc3@tsoft.com> References: <30a59ac0-28fd-f6ed-505c-9ef6d8e84fc3@tsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 9, 2023 at 6:47=E2=80=AFAM 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/peb032111a=
352_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/peb=
032111a352_s9c80d66ec1/logs/errors/readline-8.2.1.log
https://pkg-status.freebsd.org/gohan03/data/main-amd64-default-baseline/peb=
032111a352_s9c80d66ec1/logs/errors/expat-2.5.0.log
https://pkg-status.freebsd.org/gohan03/data/main-amd64-default-baseline/peb=
032111a352_s9c80d66ec1/logs/errors/libedit-3.1.20221030,1.log
etc.
Antoine
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAALwa8kAaDw80h2cbaeLOmw2G9EpRo6dJFZcFFc99mAU_7xkRA>