2d176b593b
gcc's configure system has the nasty habit (for us) of judging for
itself if it is building a cross compiler (or cross compiling), but on
the limited information of the build, host and target platforms' config
which only contains a subset of the information we encode in
`stdenv.*Platform`. The practical consequence was that prior to this
change building `pkgsLLVM.buildPackages.gcc` actually fails because it
refuses to use `--with-headers` with something it believes to not be a
cross compiler.
As a workaround we force the appropriate variable in the configure
script to always be `yes` regardless of its own conditional check.
At some point we probably should report this issue in some capacity, so
future gcc versions don't force us into workarounds like this and
|
||
---|---|---|
.. | ||
4.8 | ||
4.9 | ||
6 | ||
7 | ||
8 | ||
9 | ||
10 | ||
11 | ||
common | ||
builder.sh | ||
gfortran-darwin-NXConstStr.patch | ||
gfortran-driving.patch | ||
gnat-cflags-11.patch | ||
gnat-cflags.patch | ||
libgomp-dont-force-initial-exec.patch | ||
libphobos.patch | ||
libstdc++-netbsd-ctypes.patch | ||
libstdc++-target.patch | ||
no-sys-dirs.patch | ||
parallel-bconfig.patch | ||
ppc-musl.patch | ||
res_state-not-declared.patch | ||
sigsegv-not-declared.patch | ||
struct-sigaltstack-4.9.patch | ||
struct-sigaltstack.patch | ||
struct-ucontext-4.5.patch | ||
struct-ucontext-4.8.patch | ||
struct-ucontext-libjava.patch | ||
struct-ucontext.patch | ||
update-mcfgthread-patches.sh | ||
use-source-date-epoch.patch |