a few one-liners to try out, here's what I get (Ubuntu 18.04):
$  perl --version 2>&1 | grep version | sed -e 's/.*(v\(.*\)).*/\1/'
5.26.1
$   perl --version 2>&1 | grep version | sed -e 's/.*perl \([0-9]*\),.*/\1/'
5
$    perl --version 2>&1 | grep version | sed -e 's/.*version \([0-9]*\),.*/\1/'
26

On Tue, Apr 7, 2020 at 8:04 PM Chris Johns <chr...@rtems.org> wrote:
>
> On 2020-04-08 11:20, Gedare Bloom wrote:
> > On Tue, Apr 7, 2020 at 4:44 PM Chris Johns <chr...@rtems.org> wrote:
> >>
> >> On 2020-04-07 03:54, Gedare Bloom wrote:
> >>> On Mon, Apr 6, 2020 at 11:49 AM Joel Sherrill <j...@rtems.org> wrote:
> >>>>
> >>>>
> >>>>
> >>>> On Mon, Apr 6, 2020 at 12:43 PM Gedare Bloom <ged...@rtems.org> wrote:
> >>>>>
> >>>>> This is a problem caused by newer versions of perl. The unescaped { }
> >>>>> in regex was deprecated and then eliminated. It requires an upstream
> >>>>> fix to escape with \.
> >>>>
> >>>>
> >>>> Unfortunately, it appears that the qemu bset only works on older 
> >>>> distributions.
> >>>> The qemu4 bset is a newer qemu version that builds on newer 
> >>>> distributions.
> >>>>
> >>>> Seems to be a rat hole. It might be worth considering renaming qemu to 
> >>>> qemu2
> >>>> if that's the major version so people have to make a more conscious 
> >>>> choice.
> >>>
> >>> I think that is a good idea.
> >>
> >> Agreed.
> >>
> >>> Also, the qemu.bset could build a version of perl that would work?
> >>
> >> Could you check for the version of perl and not proceed if it is not right?
> >>
> > A little digging suggests it was deprecated with a warning in Perl
> > v5.22 and obsolete with an error in v5.26
>
> Can something similar to what I did in gdb be used to check perl's
> version ..
>
> https://git.rtems.org/rtems-source-builder/tree/source-builder/config/gdb-common-1.cfg#n83
> https://git.rtems.org/rtems-source-builder/tree/source-builder/config/gdb-common-1.cfg#n83
>
> ?
>
> Chris
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to