[Top][All Lists]

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

[sr #110350] AX_PROG_CC_FOR_BUILD broken with 2.69c

From: Zack Weinberg
Subject: [sr #110350] AX_PROG_CC_FOR_BUILD broken with 2.69c
Date: Fri, 30 Oct 2020 17:18:52 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0


                 Summary: AX_PROG_CC_FOR_BUILD broken with 2.69c
                 Project: Autoconf
            Submitted by: zackw
            Submitted on: Fri 30 Oct 2020 09:18:51 PM UTC
                Category: None
                Priority: 5 - Normal
                Severity: 3 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
        Operating System: None



>From https://lists.gnu.org/r/autoconf/2020-10/msg00048.html :

AX_PROC_CC_FOR_BUILD calls AC_PROG_CC after switching (hopefully) all
compiler variables and settings to CC_FOR_BUILD to then run the relevant

The culprit commit
requires AC_PROG_CC to be executed just once in configure which, for this
approach to make autoconf define CC_FOR_BUILD and friends, is a bridge too
far I believe.  This commit makes autoconf ignore AC_PROG_CC in
AX_PROC_CC_FOR_BUILD such that the variable CC_FOR_BUILD is empty and the
compilation command like '$CC_FOR_BUILD conftest.c' called by configure

Here a suggestion for a way out with a more careful approach assuming the
commit above be reverted: Run AC_PROG_CC and add the pair
(LANGUAGE,COMPILERNAME) to a set (say, ABC) unless the pair was already
seen, i.e. is in set ABC ('m4_set_add' could help here).  This would I think
come with the need to add optional arguments to AC_PROG_CC which would be a
step further to have autoconf itself tackle cross-compilation issues.


Reply to this item at:


  Message sent via Savannah

reply via email to

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