Date: Sun, 22 Dec 2019 16:37:35 +0000 From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 242798] sysutils/e2fsprogs: Fails to build on FreeBSD 12.1-RELEASE-p1 powerpc 32 bit: Tests failed: f_inlinedata_dirblocks Message-ID: <bug-242798-25139-uXttORXIlu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-242798-25139@https.bugs.freebsd.org/bugzilla/> References: <bug-242798-25139@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=3D242798 Matthias Andree <mandree@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Flags|maintainer-feedback?(mandre |maintainer-feedback+ |e@FreeBSD.org) | --- Comment #2 from Matthias Andree <mandree@FreeBSD.org> --- Ooops. That's bad. Unfortunately I don't have any powerpc stuff here, so I will be unable to reproduce things.=20 I have updated the port to 1.45.4 yesterday, but am not sure if powerpc32 triggers CVE-2019-5094 here - see <http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.45.4>; I know that the self-tests of 1.45.4 passed for i386, amd64 on 11.3/12.0/12= .1 and for 12.1 on MIPS64 and ARM64. So can you first retry with 1.45.4? It should have propagated to the mirrors now (for portsnap, or SVN) If that still fails, can you try recompiling wi= th WITH_DEBUG=3Dyes and then grab a backtrace from the program that caught SIG= SEGV? We may need to send that upstream to Ted Y. Ts'o if 1.45.4 still crashes. Let me know if you need more detailed instructions. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242798-25139-uXttORXIlu>