diff options
| author | Rich Felker <dalias@aerifal.cx> | 2016-04-29 19:50:33 -0400 |
|---|---|---|
| committer | Rich Felker <dalias@aerifal.cx> | 2016-04-29 19:50:33 -0400 |
| commit | 2d49c2243fbe3322961e6f0a052cc3a28acd1fe2 (patch) | |
| tree | e27680b21454a0846be8190121a406e6d65e6eba /src/network/accept.c | |
| parent | f0a61399330bae42beeb27d6ecd05570b3382a60 (diff) | |
| download | musl-2d49c2243fbe3322961e6f0a052cc3a28acd1fe2.tar.gz musl-2d49c2243fbe3322961e6f0a052cc3a28acd1fe2.tar.bz2 musl-2d49c2243fbe3322961e6f0a052cc3a28acd1fe2.tar.xz musl-2d49c2243fbe3322961e6f0a052cc3a28acd1fe2.zip | |
follow standard configure behavior for cross compile prefix
the standard configure interface, which our configure script tries to
implement, identifies cross compiling (build != host) and searches for
the properly-prefixed cross tools. our script was not doing that,
forcing users to explicitly provide either CC or a CROSS_COMPILE tool
prefix, and the more common choice, just providing CC, was incomplete
because the Makefile would still invoke the native ar and ranlib
programs. this happened to work when building on ELF-based systems
with GNU binutils, but could easily fail when cross-compiling from
dissimilar systems.
like before, and like the standard configure behavior, an explicit CC
or CROSS_COMPILE variable on the command line or in the environment
overrides the automatic prefixing.
Diffstat (limited to 'src/network/accept.c')
0 files changed, 0 insertions, 0 deletions