Date: Thu, 14 Feb 2019 19:54:40 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 234672] www/chromium: c++: error: unable to execute command: Segmentation fault (core dumped) Message-ID: <bug-234672-28929-45XYUEpnCz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234672-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-234672-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234672 --- Comment #13 from Bob Prohaska <fbsd@www.zefox.net> --- There's a seemingly unrelated bug report at https://github.com/android-ndk/ndk/issues/386 in which an i386 host cross-compiling for arm64 using clang segfaults repeatedly, much as I'm seeing in, first, chromium and then buildworld. IIUC the problem is on the arm64 side of the compiler. Most curiously, using the suggested workaround of setting CFLAGS=3D-O2 in /etc/make.conf seems to help. On the first buildworld signal 11's were seen early in buildworld but grew scarce with repetition. So far it looks as if three OS build and install cycles might be enough to flush out the problem. The bug report indicates a fix in place as of nearly a year ago. I'd think freebsd-arm would have it by now, but.... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234672-28929-45XYUEpnCz>