> applied as r10500, along with a bit to add the new files to MANIFEST.
> thanks for the patch!
>
actually, this patch failed if msvc wasn't around. it reported 'done'
instead of 'no' if msvc wasn't around, also. so, i modified the probe
a bit. you'll find the latest changes in r10504.
~jerry
On 12/13/05, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Tuesday, December 13, 2005, 7:43:07 PM, jerry gay via RT wrote:
> > applied locally, it fails on my earlier msvc install due to a version
> > comparison error:
>
> > Determining if your C compiler is actually Visual C++..Argument
> > "13.1
Tuesday, December 13, 2005, 7:43:07 PM, jerry gay via RT wrote:
> applied locally, it fails on my earlier msvc install due to a version
> comparison error:
> Determining if your C compiler is actually Visual C++..Argument "13.1.10"
> is
> n't numeric in numeric ge (>=) at config/auto/msvc.pm
> Attached patch adds a Configure test for Visual C++ compilers. For
> versions greater or equal to 14.00 (aka Visual C++ 2005)
> C<_CRT_SECURE_NO_DEPRECATE> is defined, to avoid unsafe functions
> deprecation warnings.
>
> This function or variable may be unsafe. Consider using xxx_s
> in
