gcc/gcc-final: pass TARGET_ABI flags to configure with --enable-cxx-flags

libstdc++ is in all regards a normal library, it needs to be built with TARGET_ABI flags, otherwise linking it with other C++ code may fail.

Pass TARGET_ABI flags to gcc-final configure script in the --enable-cxx-flags parameter.

Fixes:
http://autobuild.buildroot.net/results/81a3bca5cbcf789c7ce1aa221a6a4154dd7c3917/
http://autobuild.buildroot.net/results/4943b214c29951ecc7af0a1f360b6454485c0b9b/

Signed-off-by Max Filippov <[email protected]>

---
 package/gcc/gcc-final/gcc-final.mk | 4 ++++
 1 file changed, 4 insertions(+)

package/gcc/gcc-final/gcc-final.mk +4 -0

index d873aa6..8d7009b 100644
@@ -185,4 +185,8 @@ endef
 HOST_GCC_FINAL_POST_INSTALL_HOOKS += HOST_GCC_FINAL_INSTALL_USR_LIBS
 endif
 
+ifeq ($(BR2_xtensa),y)
+HOST_GCC_FINAL_CONF_OPTS += --enable-cxx-flags="$(TARGET_ABI)"
+endif
+
 $(eval $(host-autotools-package))

Quoted 2 lines · Max Filippov

libstdc++ is in all regards a normal library, it needs to be built with TARGET_ABI flags, otherwise linking it with other C++ code may fail.

Then why only do it for xtensa? And why not pass the full TARGET_CFLAGS?

Quoted 5 lines · Arnout Vandecappelle

Quoted 2 lines · Max Filippov

libstdc++ is in all regards a normal library, it needs to be built with TARGET_ABI flags, otherwise linking it with other C++ code may fail.

Then why only do it for xtensa? And why not pass the full TARGET_CFLAGS?

To minimize the impact of the change: currently it's only problem for xtensa and only TARGET_ABI flags are really missing.
Yes, passing TARGET_CFLAGS works too. And probably it works for other architectures, but that needs testing. I can send v2 with these changes.

Quoted 1 line

Quoted 1 line

Quoted 1 line

Quoted 1 line

"Arnout" == Arnout Vandecappelle <[email protected]> writes:

Quoted 5 lines · Max Filippov

Quoted 4 lines · Arnout Vandecappelle

Quoted 2 lines · Max Filippov

libstdc++ is in all regards a normal library, it needs to be built with TARGET_ABI flags, otherwise linking it with other C++ code may fail.

Quoted 6 lines

Quoted 1 line

Then why only do it for xtensa? And why not pass the full TARGET_CFLAGS?

To minimize the impact of the change: currently it's only problem for xtensa and only TARGET_ABI flags are really missing.
Yes, passing TARGET_CFLAGS works too. And probably it works for other architectures, but that needs testing. I can send v2 with these changes.

I guess we need this patch for 2015.05 then and TARGET_CFLAGS for -next.