Hi Peter.
On 01/23/2012 08:55 AM, Peter Rosin wrote:
> Stefano Lattarini skrev 2012-01-20 19:14:
>> I mean, the automake testsuite makes (or at least should make) only
>> two general assumptions about the compilers it uses:
>>
>> - they can build executables
>> - if $(build_alias) == $(host_al
Stefano Lattarini skrev 2012-01-20 19:14:
> On 01/20/2012 06:14 PM, Peter Rosin wrote:
> +
> +# The list of C++ compilers here has been copied, pasted and edited
> +# from `lib/autoconf/c.m4:AC_PROG_CXX' in the Autoconf distribution.
> +# Keep it in sync, or better again, find out a
On 01/20/2012 06:14 PM, Peter Rosin wrote:
+
+# The list of C++ compilers here has been copied, pasted and edited
+# from `lib/autoconf/c.m4:AC_PROG_CXX' in the Autoconf distribution.
+# Keep it in sync, or better again, find out a way to avoid this code
+# duplication.
>>>
Stefano Lattarini skrev 2012-01-20 15:02:
> Hi Peter.
>
> On 01/20/2012 12:56 PM, Peter Rosin wrote:
>> Stefano Lattarini skrev 2012-01-19 14:55:
>>
>> [MEGA-SNIP]
>>
>>> +# Prefer generic compilers to GNU ones when possible. This will ensure
>>> +# more testsuite coverage "in the wild".
>>> +# F
Hi Peter.
On 01/20/2012 12:56 PM, Peter Rosin wrote:
> Stefano Lattarini skrev 2012-01-19 14:55:
>
> [MEGA-SNIP]
>
>> +# Prefer generic compilers to GNU ones when possible. This will ensure
>> +# more testsuite coverage "in the wild".
>> +# FIXME: maybe we should a more comprehensive list too loo
Stefano Lattarini skrev 2012-01-19 14:55:
> * configure.ac: Look for "generic" C, C++ and Fortran compilers,
> with the aim of starting to use them in the testsuite (this will
> be done in future changes). This is more tricky than it seems,
> since we don't want to abort the whole configure script
* configure.ac: Look for "generic" C, C++ and Fortran compilers,
with the aim of starting to use them in the testsuite (this will
be done in future changes). This is more tricky than it seems,
since we don't want to abort the whole configure script even if
no one of those compilers is available (a
