--disable-rpath doesn't work in KDE3.0.1

[Michael Matz]

Hi,

On Fri, 31 May 2002, Eva Brucherseifer wrote:

> we are comiling KDE3.0.1 for Solaris at the moment, but unfortuantely the
> build option "--disable-rpath" doesn't have any effect. But the option is

Have you compiled _everything_ of interest (i.e. kdesupport, arts, kdelibs
and the others) with --disable-rpath?  The point is, if even only one lib
(the .la files) mention -R options, they will get promoted by libtool into
all libraries and apps using that lib.  So could you identify, which of
the libs from maybe arts or so, start to contain those -R's (just grep the
.la files).

> quite important on Solaris, since each SUN admins usually has his own
> location to install software.
> The package are ment for upload to ftp.kde.org
>
> Unfortunately this is quite urgent, since we are compiling on the U60 loaned
> by SUN for Linuxtag and we need to be ready on Tuesday and the machine will
> be returned on June 10th after Linuxtag.
>
> Can anyone help us please with a fast patch?

An ugly patch _not_ meant for committing, and even untested is attached.
But still I would prefer if you could identify where those -R's started to
pop up.


Ciao,
Michael.
-------------- next part --------------
Index: libtool.m4.in
===================================================================
RCS file: /home/kde/kde-common/admin/libtool.m4.in,v
retrieving revision 1.73
diff -u -p -r1.73 libtool.m4.in
--- libtool.m4.in	2002/05/16 18:16:13	1.73
+++ libtool.m4.in	2002/05/31 13:04:23
@@ -2998,6 +2998,8 @@ esac
 AC_MSG_RESULT([$_LT_AC_TAGVAR(ld_shlibs, $1)])
 test "$_LT_AC_TAGVAR(ld_shlibs, $1)" = no && can_build_shared=no
 
+_LT_AC_TAGVAR(hardcode_libdir_flag_spec, $1)=""
+
 # Figure out "hidden" C++ library dependencies from verbose
 # compiler output whening linking a shared library.
 cat > conftest.$ac_ext <<EOF
@@ -5027,6 +5029,8 @@ EOF
 ])
 AC_MSG_RESULT([$_LT_AC_TAGVAR(ld_shlibs, $1)])
 test "$_LT_AC_TAGVAR(ld_shlibs, $1)" = no && can_build_shared=no
+
+_LT_AC_TAGVAR(hardcode_libdir_flag_spec, $1)=""
 
 variables_saved_for_relink="PATH $shlibpath_var $runpath_var"
 if test "$GCC" = yes; then