From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Aring <alex.aring@googlemail.com>
Subject: Re: [ptxdist] configure failed with sed version 4.2.2
Date: Mon, 07 Jan 2013 17:38:52 +0100 [thread overview]
Message-ID: <50EAFA1C.1040006@pengutronix.de> (raw)
In-Reply-To: <CAB_54W6XWA1GYJFBRKsKgtWRtBK3cU-VXihXqCLtPek-23nCcg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2476 bytes --]
On 01/07/2013 03:19 PM, Alexander Aring wrote:
> Hello,
>
> i am using archlinux with GNU sed version 4.2.2 which generate with 'sed
> --version':
>
> sed (GNU sed) 4.2.2
> Copyright (C) 2012 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>> .
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by Jay Fenlason, Tom Lord, Ken Pizzini,
> and Paolo Bonzini.
> GNU sed home page: <http://www.gnu.org/software/sed/>.
> General help using GNU software: <http://www.gnu.org/gethelp/>.
> E-mail bug reports to: <bug-sed@gnu.org>.
> Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.
>
>
> This will fail on sed version check in configure.ac:
> SED_VERSION=`$SED --version 2>/dev/null | $SED -ne "s/.*version
> \([[0-9\.]]*\)/\1/p"`
>
>
> With command 'sed --version 2>/dev/null | sed -ne "s/.*version
> \([[0-9\.]]*\)/\1/p"' I got following output:
> "3 or later <http://gnu.org/licenses/gpl.html>."
>
> and configure failed with:
> checking sed version... configure: error: we need at least GNU sed 4.x
>
>
> GNU sed gets version string from gnulib see
> http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/version-etc.c;hb=dbed1625626c6d6f271b715f87fd0930d8e68c2f
> beginning at line 43.
>
> I don't see a "version" substring there, maybe it isn't the best way to
> match the sed version.
Since 4.2.1 the output of sed --version changed:
> $ sed --version
> GNU sed version 4.2.1
> Copyright (C) 2009 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE,
> to the extent permitted by law.
>
> GNU sed home page: <http://www.gnu.org/software/sed/>.
> General help using GNU software: <http://www.gnu.org/gethelp/>.
> E-mail bug reports to: <bug-gnu-utils@gnu.org>.
> Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.
Can you please improve the regex to parse both version of sed?
regards,
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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-01-07 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 14:19 Alexander Aring
2013-01-07 16:38 ` Marc Kleine-Budde [this message]
[not found] <CAKNcqrgFfFzNuxhi8nJBXjoHq9Lmh8t6WFau_uA3gOQQax1H6A@mail.gmail.com>
2014-07-29 13:20 ` Marc Kleine-Budde
2014-07-29 14:39 ` Kristof Verdonck
2014-07-31 8:34 ` Marc Kleine-Budde
2014-07-31 14:53 ` Kristof Verdonck
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=50EAFA1C.1040006@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=alex.aring@googlemail.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