Hi,

since it might take too long until a libtool release for some, I'll 
contribute the m4 code to patch the bug from autoconf:

m4_if(m4_cmp(m4_version_compare(LT_PACKAGE_VERSION,[2.4.6]),1),-1,
      [m4_pushdef([_LT_SYS_HIDDEN_LIBDEPS],m4_bpatsubst(m4_dquote(
         m4_defn([_LT_SYS_HIDDEN_LIBDEPS])),[test x-\([LR]\) = "\$p"],
           [test x-\1 = x"$p"]))])dnl
LT_INIT
m4_if(m4_cmp(m4_version_compare(LT_PACKAGE_VERSION,[2.4.6]),1),-1,
   [m4_popdef([_LT_SYS_HIDDEN_LIBDEPS])])dnl

Regards, Thomas

On 7/22/19 3:53 PM, Igor Rondarev via Bug-libtool wrote:
> Hi!
> 
> There is probaby a bug in 'm4/libtool.m4' that prevents correct 
> detection of all the library paths provided by compiler (comparison is 
> always FALSE). Here is a small patch:
> 
>> diff -ruN orig/m4/libtool.m4 patched/m4/libtool.m4
>> --- orig/m4/libtool.m4   2019-04-18 16:57:12.487507441 +0300
>> +++ patched/m4/libtool.m4        2019-04-18 16:57:29.503424063 +0300
>> @@ -7537,8 +7537,8 @@
>>      -L* | -R* | -l*)
>>         # Some compilers place space between "-{L,R}" and the path.
>>         # Remove the space.
>> -       if test x-L = "$p" ||
>> -          test x-R = "$p"; then
>> +       if test x-L = "x$p" ||
>> +          test x-R = "x$p"; then
>>          prev=$p
>>          continue
>>         fi
> Regards,
> Igor.
> 
> 
> 
> 
> 
> _______________________________________________
> Bug-libtool mailing list
> Bug-libtool@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-libtool