Date: Wed, 30 Dec 2020 20:05:02 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 252068] databases/cassandra4: fix aarch64/arm64 build (javadoc fails) Message-ID: <bug-252068-7788-iUK9hx6bE3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252068-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-252068-7788@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=3D252068 --- Comment #5 from Ronald Klop <ronald-lists@klop.ws> --- (In reply to Kurt Jaeger from comment #4) It works for me. https://www.klop.ws/cassandra4.0.b2-13arm64-local-workstation.log So, where is the error? My fix in this issue helped your and my build to continue past the javadoc stage so there is progress already. The build error on your system is not on my RPI4 and not on any other arch which builds cassandra4 [1]. I don't see how my patch would create this err= or.=20 In your log the "data seg size" 131072 in "--Resource limits--" seems a lot smaller than on my machine and on the amd64 beefy18 builder. Could that be = the cause of "/bin/sh argument list too long"? But I'm guessing here. It was on= e of the small differences I notices when diffing your and my build log. [1] http://beefy18.nyi.freebsd.org/data/head-amd64-default/p558707_s368819/logs= /cassandra4-4.0.b2.log --=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-252068-7788-iUK9hx6bE3>