On Tue, Oct 08, 2002 at 10:11:28AM +0100, Stewart Brodie wrote:
> In message <[EMAIL PROTECTED]>
> "John W. Eaton" <[EMAIL PROTECTED]> wrote:
> > If necessary, I could put these tools in a separate directory with an
> > independent configure script, but then what is the correct way to te
In message <[EMAIL PROTECTED]>
Andreas Schwab <[EMAIL PROTECTED]> wrote:
> Stewart Brodie <[EMAIL PROTECTED]> writes:
>
> |> This is the approach that I have taken:
> |>
> |> AC_MSG_NOTICE([configuring the tools for *native* builds])
> |> cd tools && \
> |> ./configure --build=$build_
Stewart Brodie <[EMAIL PROTECTED]> writes:
|> This is the approach that I have taken:
|>
|> AC_MSG_NOTICE([configuring the tools for *native* builds])
|> cd tools && \
|> ./configure --build=$build_alias --host=$build_alias --target=$host_alias
Note that this does not work if $srcdir != $buildd
In message <[EMAIL PROTECTED]>
"John W. Eaton" <[EMAIL PROTECTED]> wrote:
> What is the right way to use autoconf to determine the compiler and
> system characteristics for tools that are written in C and must be run
> as part of a larger build that is cross compiled?
>
> For example,
