[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad config.h on cross-build configure...
From: |
Jim Meyering |
Subject: |
Re: Bad config.h on cross-build configure... |
Date: |
Tue, 04 Nov 2003 09:46:02 +0100 |
David Daney <address@hidden> wrote:
> $ mipsel-linux-gcc --version
> mipsel-linux-gcc (GCC) 3.3.1
...
> $ ../coreutils-5.0/configure --build=i686-linux --host=mipsel-linux
> --target=mipsel-linux
>
> Results in the following lines in config.h:
...
> #define UTILS_OPEN_MAX cross compiling run-test in open-max.m4
Any time you configure in a cross-compiling environment,
you should pre-seed configure's cache with the var=val pairs
corresponding to all `run'-tests (i.e. all tests that involve
running a just-compiled-and-linked program). Then, when you
run `./configure --cache=pre-seeded-cache', none of those programs
will be (or need to be) run.
Some of the run-tests are able to fall back on less-efficient,
but guaranteed-to-work defaults. It's better to determine the
precise values for those tests that are appropriate for your
target system.