This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Python detection fallout with non GNU sed

From: Andreas Tobler <andreast-list at fgznet dot ch>
To: Joel Brobecker <brobecker at adacore dot com>
Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Wed, 02 Feb 2011 16:18:07 +0100
Subject: Re: Python detection fallout with non GNU sed
References: <4D486FE8.7040306@fgznet.ch> <20110202044534.GH2400@adacore.com>

On 02.02.11 05:45, Joel Brobecker wrote:

a recent commit to the configure.ac/configure in src/gdb broke the
machinery on machines which do not have GNU sed.

That's me, sorry.

Np.

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.)
This is not going to work on Windows, because windows the python
library does not have the dot in the version number (Eg: Python27).
I've checked in a fix. Can you retry?

This is fine with me. Tested on darwin and FreeBSD. Works perfect here.

Thank you very much for the quick fix.

Gruss,
Andreas

References:
- Python detection fallout with non GNU sed
  - From: Andreas Tobler
- Re: Python detection fallout with non GNU sed
  - From: Joel Brobecker

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]