Hi Mark, [ Explicitly doing a reply-to-all ]
2017-12-09 1:44 GMT+01:00 Mark Linimon <[email protected]>: > Modified: head/devel/arpc/Makefile > ============================================================================== > --- head/devel/arpc/Makefile Fri Dec 8 22:55:39 2017 (r455812) > +++ head/devel/arpc/Makefile Sat Dec 9 00:42:05 2017 (r455813) > @@ -19,6 +19,9 @@ LIB_DEPENDS= libargdata.so:devel/argdata > RUN_DEPENDS= > ${PYTHON_PKGNAMEPREFIX}pyPEG2>=2.15.2:textproc/py-pyPEG2@${PY_FLAVOR} \ > > ${PYTHON_PKGNAMEPREFIX}toposort>=1.5:devel/py-toposort@${PY_FLAVOR} > > +BROKEN_armv6= fails to build: *** Signal 11 > +BROKEN_armv7= fails to build: *** Signal 11 > + > USES= cmake localbase:ldflags python:3.4+ shebangfix tar:xz > python_OLD_CMD= "/usr/bin/env python3" > SHEBANG_FILES= scripts/aprotoc.py It's a shame to see this port (and the others) being marked as broken. I also wasn't aware that it was broken, as I don't think I ever saw any pkg-fallout emails. Is there a way for me to get some more insight in what's going on here? Are the full build logs available somewhere? On which versions of FreeBSD is it broken? Has it always been like this, or did it break due to the latest import of Clang? -- Ed Schouten <[email protected]> Nuxi, 's-Hertogenbosch, the Netherlands _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "[email protected]"
