[oe] [PATCH] gcc_4.2.4.bb: QA Issue: No GNU_HASH in the elf binary

[Stanislav Brabec]

Sledz, Steffen wrote:
> > > It's in all gcc versions, really.
> > 
> > No, it isn't:
> > 
> > NOTE: package gcc-4.3.3-r0: task do_build: completed

I can confirm the failure in the default angstrom build for spitz from
the last week. Linking of gcc wrapper and few other utilities reported
the standard GNU_HASH QA error.

Here is a possible fix or work-around. It's tested and it works, but
maybe it is not fully correct.

It may be one of following problems. I did not search deeper which one
is true:
- Ignoring LDFLAGS passed to configure
- LDFLAGS x LDFLAGS_FOR_TARGET clash
- LDFLAGS_FOR_TARGET are not set in cross builds of native gcc compiler
  (i. e. not canadian)

diff --git a/recipes/gcc/gcc-configure-common.inc b/recipes/gcc/gcc-configure-common.inc
index e88cee5..ef42210 100644
--- a/recipes/gcc/gcc-configure-common.inc
+++ b/recipes/gcc/gcc-configure-common.inc
@@ -73,6 +73,7 @@ do_configure () {
 	export CPPFLAGS_FOR_BUILD="${BUILD_CPPFLAGS}"
 	export CXXFLAGS_FOR_BUILD="${BUILD_CXXFLAGS}"
 	export LDFLAGS_FOR_BUILD="${BUILD_LDFLAGS}"
+	export CC="${CC} ${LDFLAGS}"
 	export ARCH_FLAGS_FOR_TARGET="${ARCH_FLAGS_FOR_TARGET}"
 	(cd ${S} && gnu-configize) || die "failure running gnu-configize"
 


________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus