[PATCH] Add run path when linking with tcc, fixing bug #20622.

Add run path when linking with tcc, fixing bug #20622. Signed-off-by: Vincent Lefevre --- m4/libtool.m4 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/m4/libtool.m4 b/m4/libtool.m4 index a3bc337..cb4fea3 100644 --- a/m4/libtool.m4 +++ b/m4/libtool.m4 @@ -5232,6 +5232,7 @@ _LT_EOF

[PATCH 0/2] AIX: Do not rely on OBJECT_MODE env var being set.

Hi! While testing --with-aix-soname=[aix|both|svr4] libtool patches within gcc, I've discovered that gcc does not set OBJECT_MODE during multilib build. Instead, the only settings done are: CC='xgcc -maix64' CXX='xg++ -maix64', besides AR="$AR -X32_64" NM="$NM -X32_64" - which feels like a workaro

[PATCH 1/2] Fix func_echo_all inside configure.

* m4/libtool.m4 (func_echo_all): Properly get $* through m4. --- m4/libtool.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/libtool.m4 b/m4/libtool.m4 index a3bc337..c42a418 100644 --- a/m4/libtool.m4 +++ b/m4/libtool.m4 @@ -1218,7 +1218,7 @@ fi # Invoke $ECHO with all a

[PATCH 2/2] AIX: Do not rely on OBJECT_MODE env var being set.

To compile 64-bit, AIX toolchain provides support to set the environment variable OBJECT_MODE=64, to avoid the need for changing anything else in the build environment. However, gcc ignores OBJECT_MODE, and does not set it while building gcc itself during its multi-lib build either. Also, CC may be

[patch #8675] elftoolchain strip support

URL: Summary: elftoolchain strip support Project: GNU Libtool Submitted by: delphij Submitted on: Sat 23 May 2015 12:20:56 AM GMT Category: None Priority: 7 - High