On Thu, May 15, 2025, at 7:52 AM, Sam James wrote:
>> AN_PROGRAM([ranlib], [AC_PROG_RANLIB])
>> +AN_PROGRAM([gcc-ranlib], [AC_PROG_RANLIB])
>> AC_DEFUN([AC_PROG_RANLIB],
>> -[AC_CHECK_TOOL(RANLIB, ranlib, :)])
>> +[AC_CHECK_TOOL(RANLIB, gcc-ranlib ranlib, :)])
>
> (The AC_CHECK_TOOL changes aren't right, needs to be called-then-
> checked, but I won't send a v2 yet as still testing it and want
> feedback on the idea of it.)
Can you elaborate a bit on "needs to be called-then-checked" please?
Your description of the problem made it _sound_ like this change (and
the matching one for ar) should be sufficient modulo tests. Is there
a situation where gcc-{ar,ranlib} are available on the PATH but
*should not* be used in preference to plain {ar,ranlib}?
zw
