[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Automake-commit] [SCM] GNU Automake branch, experimental/compilers-for-

From: Stefano Lattarini
Subject: [Automake-commit] [SCM] GNU Automake branch, experimental/compilers-for-testsuite, created. v1.11-1524-gaf2bd48
Date: Tue, 25 Oct 2011 10:24:06 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Automake".;a=commitdiff;h=af2bd48e367c2f479dd4825a2beaf683ec340ffe

The branch, experimental/compilers-for-testsuite has been created
        at  af2bd48e367c2f479dd4825a2beaf683ec340ffe (commit)

- Log -----------------------------------------------------------------
commit af2bd48e367c2f479dd4825a2beaf683ec340ffe
Author: Stefano Lattarini <address@hidden>
Date:   Fri Oct 21 19:42:50 2011 +0200

    test defs: allow compilers to be auto-selected on user's request
    In the recent changes, by pre-setting the required compilers for
    the `configure' scripts launched by the test scripts, we have
    slightly reduced the coverage of autoconf/automake code aimed at
    automatically detecting said compilers.  This commit restore such
    coverage, by allowing the user to instruct the testsuite *not* to
    preset the testsuite compiler(s).
    * tests/defs (cc): If $CC is set to the special value "autodetect"
    or "autodetected", don't export the configure-detected CC, CFLAGS
    and CPPFLAGS variables; rather, unset them.
    (c++): Likewise, but for CXX, CFLAGS and CPPFLAGS instead.
    (fortran): Likewise, but for FC and FCFLAGS instead.
    (fortran77): Likewise, but for F77 and FFLAGS instead.
    (require_compiler_): New function, to reduce code duplication.

commit ed2279d94f90cb1863d30083c4157d4594eae150
Author: Stefano Lattarini <address@hidden>
Date:   Fri Oct 21 16:50:50 2011 +0200

    test defs: substitute compilers and flags found at configure time
    * tests/ (do_subst): Also substitute CC, CXX, F77, FC,
    * tests/ Define those variables, allowing for
    overrides from the environment.
    * tests/defs (for tool in $required): Export (subsets of) those
    variables when the stuff in `$required' calls for it.
    Add related explanatory comments.

commit a0dff0aa50ddaa26c79833daf3f9d612cfcc367f
Author: Stefano Lattarini <address@hidden>
Date:   Fri Sep 23 15:47:15 2011 +0200

    test defs: setup `*FLAGS' variables for GNU compilers
    * Setup some `*FLAGS' variables for use by the
    GNU compilers in our testsuite.  For example, use `GNU_CFLAGS'
    instead of `CFLAGS', and so on for similar variables.  This
    is especially useful in case the compilers found or defined
    at configure time are not the GNU ones.
    * tests/ Initialize those same variables with
    the values set at configure time, but allowing overrides
    from the environment.
    * tests/ (do_subst): Process configure-style
    substitutions of those variables (e.g., address@hidden@').
    * tests/defs: When a GNU compiler is required, override the
    corresponding generic `*FLAGS' variable with the GNU-specific
    variant (e.g., redefine `$CFLAGS' to take the value of

commit 149778d116cda269ae8df142dd07019a3eb33301
Author: Stefano Lattarini <address@hidden>
Date:   Fri Sep 23 00:00:22 2011 +0200

    configure: search generic compilers for use in the tests
    * 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 (after all, they're only
    needed by the testsuite, not to build automake), but currently
    autoconf doesn't offer an easy way to obtain this behaviour.
    We prefer non-GNU compilers to the GNU ones, to ensure better
    coverage "in the wild".


GNU Automake

reply via email to

[Prev in Thread] Current Thread [Next in Thread]