On 2023 May 13 (Sat) at 18:08:52 +0200 (+0200), Theo Buehler wrote:
:On Sat, May 13, 2023 at 05:37:01PM +0200, Peter Hessler wrote:
:> On 2023 May 13 (Sat) at 17:22:55 +0200 (+0200), Theo Buehler wrote:
:> :> 
http://build-failures.rhaalovely.net/aarch64/2023-05-11/net/unison,no_x11.log
:> :
:> :As already mentioned elsewhere, this is the strange USE_NOEXECONLY
:> :thing that affects some ocaml ports on aarch64. I think it should be
:> :marked as such on aarch64 until someone figures out why this is needed
:> :for aarch64 and not amd64.
:> 
:> I tried that, but it doesn't make a difference when building on my X13s.
:
:This builds and packages both flavors on my m1. I use llvm15 on it, so
:it could be a difference in code generation. If that doesn't work for
:you, I guess we have to mark it BROKEN-aarch64 until we update to llvm15
:

Could be code generation, it doesn't build for me with in-tree llvm13.

OK for this, and we can probably also add BROKEN-aarch64 at the same
time.


:Index: Makefile
:===================================================================
:RCS file: /cvs/ports/net/unison/Makefile,v
:retrieving revision 1.22
:diff -u -p -r1.22 Makefile
:--- Makefile   28 Apr 2023 06:01:41 -0000      1.22
:+++ Makefile   13 May 2023 16:06:53 -0000
:@@ -1,3 +1,7 @@
:+.if ${MACHINE_ARCH} == aarch64
:+USE_NOEXECONLY = yes
:+.endif
:+
: COMMENT =     multi-platform file synchronization tool
: 
: GH_ACCOUNT =  bcpierce00

-- 
The goal of science is to build better mousetraps.
The goal of nature is to build better mice.

Reply via email to