Source-Changes-D archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: src/external/apache2/llvm/config/llvm/Config



So host needs to install terminfo-dev. How is that different from the host environment needing to provide other pieces of the development environment? For example if another tool needed openssl-dev, would we disable crypto? Or if it needed yacc/bison or autoconf/automake wouldn't we rather install those? Isn't simple to type one command to install the appropriate packages?

christos

christos



> On Feb 20, 2020, at 7:32 PM, Kamil Rytarowski <n54%gmx.com@localhost> wrote:
> 
> On 21.02.2020 01:17, Christos Zoulas wrote:
>> In article <5f8df6c1-bb25-f24a-27fc-b3a752a6db78%gmx.com@localhost>,
>> Kamil Rytarowski  <n54%gmx.com@localhost> wrote:
>> 
>>> We don't have any direct reproducer (we tried) and we must figure it out
>>> from syzkaller bot. We don't have access to the machine and a limited
>>> access to an admin over there (who has no expertise on BSDs). This
>>> failure breaks kMSan build for long time now. There is full build log.
>> 
>> If we don't undestand the problem we don't just disable code to make the
>> tool happy. This is: hand hurts, amputate. Let's try to figure out what's
>> wrong first.
>> 
>>> Calling syzbot report useless does not help. Lack of support in the
>>> build phase will result in removal of the bot instance and turn our work
>>> into futile effort.
>> 
>> We need to have more details in order to fix the problem.
>> 
>> christos
>> 
> 
> ./build.sh tools for LLVM is broken when host ships with no terminfo
> devel libraries. I tried to disable this superfluous feature for tools
> (for colors in a terminal), but it got reverted (breaking TNF rules) here.
> 
> The broken tools logic was workarounded in the syzbot setup and we
> installed there ncurses-dev package and the build passed.
> 
> PR toolchain/54993
> 
> <sanitizer.log>



Home | Main Index | Thread Index | Old Index