Re: New version checking routine fails if version number is in the full path

[Mats Bengtsson]

(Needless to say, it seems that the old routine worked "by chance"
in this situation, since it picked the version number from the path
not from the output of the command.)

What I don't really understand is why you include the full path in
$exe, why not simply use the command name and let shell find it
(it should find the same executable as 'type -p' anyway). If I just
replace the current definition of $exe with
exe= $r
everything works fine.

  /Mats

Mats Bengtsson wrote:

> Hi,
>
> On my system, the latest Python version is installed in
> /pkg/python/2.4.2/os/bin/python
> and it seems that the new version checking routine in configure
> fails in such situations. I haven't deciphered exactly how you
> expect it to work, but if I remove the final | sed 's/\([0-9.]*\).*/\1/g'
> _ver will be
> /pkg/python/2.4.2/os/bin/python
> instead of
> 2.4.2
>
>   /Mats

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================