Re: Autoconf and a bare-metal host with no C library

[Robert Woodworth]

I don't have an example, but I have done this in the past.

Autoconf need to know that the host and target are different, then it will
not try the 'native' CC to check for local executable.

On Thu, Oct 13, 2016 at 8:48 AM, Keith Marshall <
address@hidden> wrote:

> On 13/10/16 15:24, Russell Shaw wrote:
> > On 13/10/16 13:11, Luca Saiu wrote:
> >
> > ...
> > > So, what I'm asking you is: does a clean solution exist, or compiling
> > > without a runtime library is just not supported by the Autotools?  It
> > > sounds weird to say that for configuring you need a cross-compiler with
> > > support for a runtime that will never even be linked when building.
> > > Shouldn't there be, at least, one variant of AC_PROG_CC which doesn't
> > > fail in a fatal way?
> > >
> > > I'm not yet linking the code in a public forum just because it still
> > > lacks copyright and license headers; but in case it were useful to you,
> > > even if I doubt it, I can clean it up and publish it.
> >
> > It can be messy and take quite some time to figure out what to do, but
> this kind
> > of stuff is handled in the autoconf/automake/autogen build system of
> binutils
> > and gcc. Not a quick and easy path for the uninitiated though.
>
> Or maybe, you could consider something along the lines of
> MINGW_AC_PROG_CC_COMPILE_ONLY, (and associated support macros), as
> included within this aclocal.m4:
> https://sourceforge.net/p/mingw/mingw-org-wsl/ci/5.0-
> active/tree/aclocal.m4
>
> --
> Regards,
> Keith.
>
>
> _______________________________________________
> Autoconf mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/autoconf
>