Re: Link programs with libraries within a staging directory

[Ralf Wildenhues]

Hello Pierre,

* Pierre Pronchery wrote on Sun, Jul 05, 2009 at 01:37:58PM CEST:
> us hackable:1 developers [1] have been cross-compiling libtool-based
> projects for a while. We are using a staging directory where libraries
> and programs are installed as they are compiled.
> 
> Unfortunately, libtool was consistently failing at using the right
> absolute path to the libraries there, picking up native libraries of the
> same name instead. We've come up with this patch to solve the situation
> in our case, together with the -inst-prefix-dir flag. I don't think it
> has any side-effects either.

Please provide a preferably small, reproducible example that fails
without but not with the patch.  State the Libtool version used, and
the system this happens on, preferably all with `./libtool --config'.

I don't think the patch is right, but it's easier for me to look at an
example to state why.

Thanks,
Ralf

> --- a/libltdl/config/ltmain.m4sh
> +++ b/libltdl/config/ltmain.m4sh
> @@ -5333,9 +5333,11 @@ func_mode_link ()
>           fi
>           if test "$linkmode" = prog; then
>             test -n "$add_dir" && compile_deplibs="$add_dir $compile_deplibs"
> +           test -f "$inst_prefix_dir$add" && add="$inst_prefix_dir$add"
>             test -n "$add" && compile_deplibs="$add $compile_deplibs"
>           else
>             test -n "$add_dir" && deplibs="$add_dir $deplibs"
> +           test -f "$inst_prefix_dir$add" && add="$inst_prefix_dir$add"
>             test -n "$add" && deplibs="$add $deplibs"
>             if test "$hardcode_direct" != yes &&
>                test "$hardcode_minus_L" != yes &&