This set of changes ensures that TARGET_CC_ARCH is passed reliably to all

packages in a build.  The change fixes problems in the following packages:
binutils{,-cross}_2.15.94.0.1
	HOST_CC_ARCH was not being passed to HOST_CC.  The problem does
	not seem to be present in binutils* 2.16, however this version
	is still used for uClibc builds.
gcc{,-cross,-cross-initial}_3.4.4
	HOST/TARGET_CC_ARCH was not used in the appropriate places, plus
	this was not sufficient - FLAGS_FOR_TARGET (a gcc make variable)
	is now preloaded with the target CC_ARCH values, which causes all
	the builds (gcc, g++, gcj, fortran) to get the correct values.
gcc OTHER
	*NOT* fixed - other versions of gcc will still need the _CC_ARCH
	fix in the same lines (CC_FOR_TARGET, GCC_FOR_TARGET, CXX_FOR_TARGET),
	however so long as these builds use gcc3-*.inc the FLAGS_FOR_TARGET
	fixx will be there.
uclibc{,-initial}_0.9.27
	TARGET_CC_ARCH added to the do_compile.  For the do_stage step the
	build actually compiles target code (make utils), but this will not
	accept a CC with whitespace.  The TARGET_CC_ARCH flags have therefore
	been added to CFLAGS (a bit ugly, but it works).
These changes have been tested for both cross and target builds, the changes
should be fine on self-hosted (i.e. target-hosted) builds, if anyone actually
does these, but note that the gcc build specifically tests for build==host and
does *not* do certain _FOR_TARGET settings in this case (this was the case
before this change too) - if you are seeing strange settings on self-hosted
gcc builds (before and after this change) check the do_compile environment
variable settings.

0 files changed, 0 insertions, 0 deletions