question about running autoconf in newlib directory

Luca Barbato
Tue Jul 30 21:00:00 GMT 2013

On 30/07/13 22:16, Jeff Johnston wrote:
> A long while back, we got around a problem in autoconf AC_PROG_CC which
> tries and build an executable to verify that the compiler is valid. 
> Since we are building the library, this doesn't work.  The following is
> documented in our acinclude.m4:
> # FIXME: We temporarily define our own version of AC_PROG_CC. This is
> # copied from autoconf 2.12, but does not call AC_PROG_CC_WORKS. We
> # are probably using a cross compiler, which will not be able to fully
> # link an executable.  This should really be fixed in autoconf
> # itself.
> It is likely that some new check added in the current autoconf is noting
> we haven't called the base AC_PROG_CC macro and what it subsequently
> calls.  Although I have seen such warnings, I haven't seen any build
> issues so I have just left it alone for the time-being.

What about biting the bullet and rewrite the whole thing from scratch
using a modern autotool version?

Probably would be faster, more compact and easier to grok.


More information about the Newlib mailing list