[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multilib dirs and ld.so
From: |
Peter O'Gorman |
Subject: |
Re: multilib dirs and ld.so |
Date: |
Wed, 05 Sep 2007 23:42:53 -0500 |
On Thu, 2007-09-06 at 00:25 +0200, Ralf Wildenhues wrote:
Hi Ralf, thank you for testing!
> Further, the indiscriminate use of ldd, or absolute file names in the
> test of course prevents decent cross-compile results. (Not that this
> is much of a regression, the problem existed before.)
>
> Ideally, I would like, in a system that also uses symlinks, to see
> both the symlink and the real dir present in the search path.
>
> We should consider just making this whole setting overridable at
> configure time.
which makes me think maybe doing the simple thing:
<crap>
sys_lib_dlsearch_path_spec64='/lib64 /usr/lib64'
sys_lib_dlsearch_path_spec32='/lib32 /usr/lib32'
sys_lib_dlsearch_path_specfoo='/lib /usr/lib'
if 32bitbuild
sys_lib_dlsearch_path_spec="$sys_lib_dlsearch_path_spec32
$sys_lib_dlsearch_path_specfoo $sys_lib_dlsearch_path_spec64
$lt_ld_extra"
else
sys_lib_dlsearch_path_spec="$sys_lib_dlsearch_path_spec64
$sys_lib_dlsearch_path_specfoo $sys_lib_dlsearch_path_spec32
$lt_ld_extra"
fi
</crap>
all inside an AC_CACHE_VAL() (that sets and tests an lt_cv_var) so it
can be overridden and so forth, is the best plan.
Sigh, indeed.
If you think that a 1.5.26 release is urgent, I won't insist that you
wait on this.
Thanks,
Peter