This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Python detection fallout with non GNU sed
- From: Andreas Tobler <andreast-list at fgznet dot ch>
- To: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Tue, 01 Feb 2011 21:41:12 +0100
- Subject: Python detection fallout with non GNU sed
Hi all,
a recent commit to the configure.ac/configure in src/gdb broke the
machinery on machines which do not have GNU sed.
The issue is the following:
sed -e 's,^.* -l\(python[0-9]*[.]\?[0-9]*\).*$,\1,'`
On certain sed implementations the quantifier '\?' can not be used on
backreferences.
This breaks the detection of python.
Here it fails on darwin and FreeBSD.
I tried the follwoing on those systems and on linux-ppc:
sed -e 's,^.* -l\(python[0-9]*[.][0-9]*\).*$,\1,'`
(the same expression w/o the \? quantifier.)
So far I do not see a drawback. But maybe I did not cover all aspects.
I do not have a *win* system to test on.
What do you think?
Gruss,
Andreas