Re: Wrong "ar" used when cross-building lttng

[Simon Marchi <simark@simark.ca>]

On 2019-11-15 3:18 a.m., Rolf Eike Beer wrote:
> Simon Marchi wrote:
>> On 2019-11-14 11:24 a.m., Rolf Eike Beer wrote:
> 
>>> I have not checked latest git, but maybe you may want to fix this warning,
>>> too?
>>>
>>> With 2.11.0 release tarball:
>>>
>>> -./configure: line 24663: test: -eq: unary operator expected
> 
>> Hmm I don't remember seeing this error, and I don't see it now.
>>
>> Could you please try with master?  If it still happens, you can try to
>> find from which line of the configure.ac or an m4 file this line comes
>> from.  I presume it won't be too hard to fix.
> 
> Sorry, my fault. If I had looked a little closer I could have given you the 
> context:
> 
>  checking for tput... /usr/bin/tput
>  tput: No value for $TERM and no -T specified
> ./configure: line 24663: test: -eq: unary operator expected
> 
> When the package is built inside our automated buildsystem these variables are 
> not set because this is no interactive shell. If I build with an interactive 
> shell these warnings are in fact not there.

It still sounds like the "test" command should be improved, it should not fail with
an invalid syntax.  Can you give us the relevant lines of configure around 24663,
and if possible match them to the source lines in configure.ac and/or one of the
m4 files in the m4 directory?

Simon