This is the mail archive of the
mailing list for the newlib project.
Re: question about running autoconf in newlib directory
- From: Luca Barbato <lu_zero at gentoo dot org>
- To: newlib at sourceware dot org
- Date: Tue, 30 Jul 2013 23:00:04 +0200
- Subject: Re: question about running autoconf in newlib directory
- References: <298bd647-549f-4187-9d1f-5036d8dbc68e at BAMAIL02 dot ba dot imgtec dot org> <51F81F2C dot 5000000 at redhat dot com>
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.