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

2020-02-20 Thread Martin Husemann
On Fri, Feb 21, 2020 at 03:01:45AM +0100, Kamil Rytarowski wrote: > I consider calling ncurses-dev essential as a bug. My knee jerk reaction was: if a unix compiler needs terminfo (especially when it only does that to create coloured unreadable messages) it needs to be moved to pkgsrc. Same goes f

Re: CVS commit: src/doc

2020-02-20 Thread Christos Zoulas
Yup, I have those in /etc/mk.conf. HAVE_LLVM=yes MKLLVM=yes MKGCC=no $ fgrep netbsd-clang /usr/src/make.sparc64-sparc64.release.out | head -4 --- sparc64--netbsd-clang --- # link llvm-clang/sparc64--netbsd-clang c++ -g -O2 -fno-rtti -fno-exceptions -fno-strict-aliasing -I/usr/obj/sparc64-s

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

2020-02-20 Thread Kamil Rytarowski
On 21.02.2020 02:47, Christos Zoulas wrote: > 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

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

2020-02-20 Thread Christos Zoulas
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 insta

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

2020-02-20 Thread Kamil Rytarowski
On 21.02.2020 01:17, Christos Zoulas wrote: > In article <5f8df6c1-bb25-f24a-27fc-b3a752a6d...@gmx.com>, > Kamil Rytarowski 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

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

2020-02-20 Thread Christos Zoulas
In article <5f8df6c1-bb25-f24a-27fc-b3a752a6d...@gmx.com>, Kamil Rytarowski 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

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

2020-02-20 Thread Valery Ushakov
On Thu, Feb 20, 2020 at 00:09:28 +, Roy Marples wrote: > On 19/02/2020 22:29, Kamil Rytarowski wrote: > > Why do you need terminfo/termios in ./build.sh tools? > > We build the nbtic tool so we can build the terminfo database. The database is not a problem. If we want to keep this code turn

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

2020-02-20 Thread Valery Ushakov
On Thu, Feb 20, 2020 at 10:54:50 +0100, Kamil Rytarowski wrote: > >> https://syzkaller.appspot.com/text?tag=CrashLog&x=11aafc09e0 > > > > Yes and that is completely useless for figuring out the why. > > We don't have any direct reproducer (we tried) and we must figure it > out from syzkaller

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

2020-02-20 Thread Kamil Rytarowski
On 20.02.2020 01:09, Roy Marples wrote: > On 19/02/2020 22:29, Kamil Rytarowski wrote: >> Why do you need terminfo/termios in ./build.sh tools? > > We build the nbtic tool so we can build the terminfo database. > > Roy I will try to have a look and switch to our internal terminfo. signature.a

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

2020-02-20 Thread Kamil Rytarowski
On 19.02.2020 23:50, Joerg Sonnenberger wrote: > On Wed, Feb 19, 2020 at 11:29:09PM +0100, Kamil Rytarowski wrote: >> On 19.02.2020 23:03, Joerg Sonnenberger wrote: >>> On Wed, Feb 19, 2020 at 04:10:17PM +0100, Kamil Rytarowski wrote: On 19.02.2020 14:32, Joerg Sonnenberger wrote: > Module

Re: CVS commit: src/doc

2020-02-20 Thread Kamil Rytarowski
On 20.02.2020 01:42, Christos Zoulas wrote: > Not reproducible: As reported this needs specified: -V MKLLVM=yes -V MKGCC=no -V HAVE_LLVM=yes > >          build.sh command:    ./build.sh -P -U -E -x -m sparc64 -a > sparc64 -D /usr/obj/sparc64-sparc64/release -R > /usr/obj/sparc64-sparc64/media -