Russ Allbery wrote:
"Dr. David Kirkby" writes:
Russ Allbery wrote:
That macro is using a questionable technique to accomplish this (parsing
the output of perl -v and then relying on AX_COMPARE_VERSION). Here's a
much simpler macro that accomplishes the same thing:
AC_DEFUN([AX_PROG_PERL_VE
"Dr. David Kirkby" writes:
> Russ Allbery wrote:
>> "Dr. David Kirkby" writes:
>>> Russ Allbery wrote:
That macro is using a questionable technique to accomplish this (parsing
the output of perl -v and then relying on AX_COMPARE_VERSION). Here's a
much simpler macro that accompli
Russ Allbery wrote:
"Dr. David Kirkby" writes:
Russ Allbery wrote:
"Dr. David Kirkby" writes:
Russ Allbery wrote:
That macro is using a questionable technique to accomplish this (parsing
the output of perl -v and then relying on AX_COMPARE_VERSION). Here's a
much simpler macro that accom
Sun Microsystems have donated a Sun T5240 (16 core) machine to the
University of Washington for Sage development.
http://www.sagemath.org/
Any *serious* developer of a project used in Sage (which includes
autoconf), would be permitted access to the machine for testing autoconf.
You probably
Dr. David Kirkby wrote:
Russ Allbery wrote:
"Dr. David Kirkby" writes:
Russ Allbery wrote:
"Dr. David Kirkby" writes:
Russ Allbery wrote:
That macro is using a questionable technique to accomplish this
(parsing
the output of perl -v and then relying on AX_COMPARE_VERSION).
Here's a
mu
On Fri, 2009-08-07 at 21:51 +0100, Dr. David Kirkby wrote:
> Do you have a better idea how to tell what linker gcc uses?
Why do you actually care? Surely what you want to know is what options
work on the linker that you have to hand? So you will need to test the
linker options you want to use, if
"Dr. David Kirkby" writes:
> Oops, I marked the wrong line!! The error is on 4686 anyway, but I did not
> even show that correctly.
Sorry, I was really too tired when I wrote that and didn't pay attention
to what I'm doing. Here's an actually tested version.
AC_DEFUN([AX_PROG_PERL_VERSION],
[A