On Tue, 06 Mar 2018 18:08:48 -0500 "Aaron M. Ucko" <u...@debian.org> wrote:
> Source: seqan2
> Version: 2.4.0+dfsg-8
> Severity: normal
> Tags: upstream
> User: debian-sp...@lists.debian.org
> Usertags: sparc64
> Builds of seqan2 for sparc64 (admittedly not a release architecture)
> have been failing lately, per the below excerpt from . The tests
> that "Failed" generally if not always returned -10, presumably
> corresponding to having encountered SIGBUS (10 on this architecture)
> -- no surprise,
Yes, upstream is aware.
> since sparc64 is notoriously strict about memory
> access alignment.
Can you expand upon this? Is there a guide for correcting this issue?