Date: Tue, 01 Aug 2017 10:42:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 221114] devel/bazel fix build on i386 Message-ID: <bug-221114-13-FEPxCON7u0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221114-13@https.bugs.freebsd.org/bugzilla/> References: <bug-221114-13@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=3D221114 --- Comment #3 from Klaus Aehlig <aehlig@linta.de> --- (In reply to Kubilay Kocak from comment #2) The port passes portlint (the port is a master port, hence the ?=3D for MAINTAINER is OK and the only occurrence of a plain "file" is in the error message in the BROKEN statement). I don't have a 32-bit system at hand, but I can confirm the following. - The port still build cleanly on am64 and the resulting binary works (not surprising, as nothing changed there). - It also builds cleanly and works if the EXTRA_PATCH is applied unconditionally. What the extra patch does, is switching back to the java-implementation of singlejar that was also used in the previous bazel release everywhere (hence also was successfully used on i386). So I'm pretty confident that this solv= es the issue, but I didn't do a QA run on i386. Hence I would appreciate, if an i386 QA run would be done. --=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-221114-13-FEPxCON7u0>