Re: libuv i386 build failure

[Michael Parson <mparson%bl.org@localhost>]

On Tue, 19 Sep 2017, Patrick Welche wrote:

> Working on pkgsrc on someonelse(tm)'s system, which has:
>
> netbsd# echo $SHELL
> /bin/csh

This is a perl problem, not a shell problem.

> Building libuv on this -current/i386 system fails with:
>
> ===> Configuring for libuv-1.14.1
> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/pkgsrc/devel/libuv/work.i386/.tools/bin/au
> tomake line 3936.
> test: : bad number
> test: : bad number
> + libtoolize --copy
> + aclocal -I m4
> + autoconf
> + automake --add-missing --copy
> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/pkgsrc/devel/libuv/work.i386/.tools/bin/au
> tomake line 3936.
> *** Error code 255
>
> Stop.
> make[1]: stopped in /usr/pkgsrc/devel/libuv
> *** Error code 1
>
>
> No "test" in sight in the automake bit (line 3936 is the regex):
>
> # substitute_ac_subst_variables ($TEXT)
> # -------------------------------------
> # Replace any occurrence of ${FOO} in $TEXT by @FOO@ if FOO is an AC_SUBST
> # variable.
> sub substitute_ac_subst_variables
> {
>  my ($text) = @_;
>  $text =~ s/\${([^ \t=:+{}]+)}/substitute_ac_subst_variables_worker ($1)/ge;
>  return $text;
> }
>
> This is perl 5, version 26, subversion 0 (v5.26.0) built for i386-netbsd-thread-multi

Yeah, I'm running 6.1 and last week did a big update to my pkgsrc stuff
to 2017Q2 and am now getting notifications like:

  Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^(.{ <-- HERE ,200}).*$/ at /usr/pkg/lib/perl5/vendor_perl/5.26.0/Mail/SpamAssassin/PerMsgStatus.pm line 921.

Using:

  $ perl -v

  This is perl 5, version 26, subversion 0 (v5.26.0) built for x86_64-netbsd-thread-multi

> Didn't get as far as running configure, which is where I would have
> expected loads of "if test"...
>
> Thoughts?

Looks like we're going to have to go around escaping '{' to keep
stuff working, kinda like we had to do to the '@' char back in the
perl4->perl5 days.

File a bug upstream?

--
Michael Parson
Pflugerville, TX
KF5LGQ