I'm using an ancient ptxdist, but that doesn't matter because I'm isolating
the SED-version check.

If I run the regex from
http://git.pengutronix.de/?p=ptxdist.git;a=blob;f=configure.ac;h=22c8df03a8c225514a3df7ba4c9fb29c515c3e24;hb=HEAD
sed --version 2>/dev/null | sed -ne "1
s/.*GNU.*\s\([[0-9\+\.]]\+\).*/\1/p" then
it returns empty, both with sed 4.2.1 and 4.2.2.


2014-07-29 15:20 GMT+02:00 Marc Kleine-Budde <mkl@pengutronix.de>:

> Hello Kristof,
>
> thanks for your mail, please use the ptxdist mailinglist (Cc'ed) in the
> future.
>
> On 07/29/2014 03:08 PM, Kristof Verdonck wrote:
> > I had a problem with the ptxdist configure script for checking the SED
> > version.
>
> Which version of ptxdist are you using?
>
> > Apparently this is a known issue that hasn't been fixed yet.
> > https://www.mail-archive.com/ptxdist@pengutronix.de/msg06717.html
>
> I think the problem has been fixed with the patch:
>
>     2a89985 configure.ac: change regex for sed version
>
> > I took the regular expression GLIBC used to check the SED version.
> > I tested it with sed 3.02.80, 4.1.5, 4.2.1 and 4.2.2
> > I thought you could use this.
> >
> > SED_VERSION=`$SED --version 2>/dev/null | $SED -n "s/^.*GNU sed[^0-9]*
> > \([0-9]*\.[0-9.]*\).*$/\1/p"`
>
> AFAIK we don't have any problems with sed since the above patch in
> mainline, which is ptxdist-2013.01.0.
>
> Marc
>
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>