From: Kristof Verdonck <kristof.verdonck@gmail.com>
To: ptxdist <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] configure failed with sed version 4.2.2
Date: Tue, 29 Jul 2014 16:39:02 +0200 [thread overview]
Message-ID: <CAKNcqrjQ7-ALHPKfnFsv21ser-amgsX1YST84X9sN4w9n4Fryg@mail.gmail.com> (raw)
In-Reply-To: <53D79F97.9060804@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1656 bytes --]
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 |
>
>
[-- Attachment #1.2: Type: text/html, Size: 2928 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-07-29 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKNcqrgFfFzNuxhi8nJBXjoHq9Lmh8t6WFau_uA3gOQQax1H6A@mail.gmail.com>
2014-07-29 13:20 ` Marc Kleine-Budde
2014-07-29 14:39 ` Kristof Verdonck [this message]
2014-07-31 8:34 ` Marc Kleine-Budde
2014-07-31 14:53 ` Kristof Verdonck
2013-01-07 14:19 Alexander Aring
2013-01-07 16:38 ` Marc Kleine-Budde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKNcqrjQ7-ALHPKfnFsv21ser-amgsX1YST84X9sN4w9n4Fryg@mail.gmail.com \
--to=kristof.verdonck@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox