Re: multimedia/libvpx cause clang fatal error on CURRENT

Is this the same issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225488 ? That was fixed in r328513. Please try that revision if you're not at it yet. On Mon, Jan 29, 2018 at 7:57 PM, Iblis Lin wrote: > Hi, > > I got this while building multimedia/libvpx > >

Re: How to avoid building of all llvm/clang-related stuff on recent CURRENT?

On 30/01/2018 09:33, Dimitry Andric wrote: > On 29 Jan 2018, at 20:56, Lev Serebryakov wrote: >> >> I have these lines in my nanobsd config: >> >> WITHOUT_CROSS_COMPILER=yes >> WITH_SYSTEM_COMPILER=yes >> WITHOUT_CLANG=yes >> WITHOUT_CLANG_EXTRAS=yes >>

multimedia/libvpx cause clang fatal error on CURRENT

Hi, I got this while building multimedia/libvpx ``` cc -O2 -pipe -march=native ... #0: t25: v8i64 = llvm.x86.avx512.psad.bw.512 TargetConstant:i64<5820>, t11, t5 fatal error: error in backend: Do not know how to split the result of this operator! cc: error: clang frontend command failed

Re: How to avoid building of all llvm/clang-related stuff on recent CURRENT?

It is not part of ELFTOOLCHAIN? -- // Lev Serebryakov -Original Message- From: Dimitry Andric To: l...@freebsd.org Cc: freebsd-current Sent: Tue, 30 Jan 2018 2:04 Subject: Re: How to avoid building of all llvm/clang-related stuff on

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > On 29 Jan 2018, at 19:39, O. Hartmann wrote: >> >> Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and >> performed >> updates of the ports tree. Since Sunday, I receive

Re: How to avoid building of all llvm/clang-related stuff on recent CURRENT?

On 29 Jan 2018, at 20:56, Lev Serebryakov wrote: > > I have these lines in my nanobsd config: > > WITHOUT_CROSS_COMPILER=yes > WITH_SYSTEM_COMPILER=yes > WITHOUT_CLANG=yes > WITHOUT_CLANG_EXTRAS=yes > WITHOUT_CLANG_BOOTSTRAP=yes > WITHOUT_BINUTILS=yes >

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

On 29 Jan 2018, at 19:39, O. Hartmann wrote: > > Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and > performed > updates of the ports tree. Since Sunday, I receive segmenatation faults (SIG > 11) when > accessing the server, especially with setup

Re: Kernel build error rev.328485

On Saturday, January 27, 2018 06:54:03 PM Per Gunnarsson wrote: > I am back with new build errors. If I post too frequently, please inform me. These all look like you have stale sources in your tree somehow (e.g. sys/compat/freebsd/freebsd32_misc.c doesn't seem to match

How to avoid building of all llvm/clang-related stuff on recent CURRENT?

I have these lines in my nanobsd config: WITHOUT_CROSS_COMPILER=yes WITH_SYSTEM_COMPILER=yes WITHOUT_CLANG=yes WITHOUT_CLANG_EXTRAS=yes WITHOUT_CLANG_BOOTSTRAP=yes WITHOUT_BINUTILS=yes WITHOUT_BINUTILS_BOOTSTRAP=yes WITHOUT_ELFTOOLCHAIN=yes WITHOUT_ELFTOOLCHAIN_TOOLS=yes

CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and performed updates of the ports tree. Since Sunday, I receive segmenatation faults (SIG 11) when accessing the server, especially with setup of nextcloud, refdb, phpldapadmin and any other access with LDAP backend (all

Re: Error compiling isboot-kmod

On Mon, 2018-01-29 at 10:29 -0700, John Nielsen wrote: > > > > On Jan 27, 2018, at 9:20 AM, Ian Lepore wrote: > > > > On Fri, 2018-01-26 at 23:20 -0700, John Nielsen wrote: > > > > > > > > > > > > > > > On Jan 26, 2018, at 9:42 PM, John Nielsen > > > >

Re: Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

[ resending from correct email address ] > On Jan 29, 2018, at 6:05 AM, Maurizio Vairani wrote: > > I am running > # uname > -a > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 > UTC 2018 >

Re: Error compiling isboot-kmod

> On Jan 27, 2018, at 9:20 AM, Ian Lepore wrote: > > On Fri, 2018-01-26 at 23:20 -0700, John Nielsen wrote: >>> >>> On Jan 26, 2018, at 9:42 PM, John Nielsen wrote: >>> [...] >>> --- iscsi.o --- >>> iscsi.c:1146:3: error: incompatible pointer

Re: r 328531: installworld failure: /usr/share/man/man3/cap_syslog.3.gz: No such file or directory

Am Mon, 29 Jan 2018 13:58:33 +0100 Mariusz Zaborski schrieb: > On Mon, Jan 29, 2018 at 06:31:31AM +0100, O. Hartmann wrote: > > > > "make installworld' fails on r328531 with the follwoing error: > > > > [...] > > --- maninstall --- > > rm -f

Fatal trap 12 booting FreeBSD-CURRENT via isboot kernel module.

I am running # uname -a FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328383: Thu Jan 25 04:48:52 UTC 2018 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 After compiling the kernel module as discussed in this thread :

Re: r 328531: installworld failure: /usr/share/man/man3/cap_syslog.3.gz: No such file or directory

On Mon, Jan 29, 2018 at 06:31:31AM +0100, O. Hartmann wrote: > > "make installworld' fails on r328531 with the follwoing error: > > [...] > --- maninstall --- > rm -f /usr/share/man/man3/cap_syslog.3 /usr/share/man/man3/cap_syslog.3.gz; > install -l > h /usr/share/man/man3/cap_syslog.3.gz

Re: Error compiling isboot-kmod

2018-01-27 17:20 GMT+01:00 Ian Lepore : > On Fri, 2018-01-26 at 23:20 -0700, John Nielsen wrote: > > > > > > On Jan 26, 2018, at 9:42 PM, John Nielsen wrote: > > > > > > > > > > > [...] > > > --- iscsi.o --- > > > iscsi.c:1146:3: error: incompatible pointer

r 328531: installworld failure: /usr/share/man/man3/cap_syslog.3.gz: No such file or directory

"make installworld' fails on r328531 with the follwoing error: [...] --- maninstall --- rm -f /usr/share/man/man3/cap_syslog.3 /usr/share/man/man3/cap_syslog.3.gz; install -l h /usr/share/man/man3/cap_syslog.3.gz /usr/share/man/man3/cap_syslog.3.gz install: link