Paul Menzel

For failing *build_dox* I created https://github.com/seqan/seqan/issues/2366. ``` […] Start 421: app_test_seqan_tcoffee 421/434 Test #421: app_test_seqan_tcoffee ............................................................***Failed 1.50 sec Comparing /dev/shm/seqan/apps/seqan_tcoffee/tests/1aab.mlocal.fasta against /tmp/tmpe9mbl8/1aab.mlocal.fasta --- +++ @@ -1,8 +1,8 @@ >hmgl_trybr -KKDSNAPKRAMTSFMFFSSDFRS----KHSDLS-IVEMSKAAGAAWKELGPEERKVYEEM...

On 12/05/18 12:50, rrahn wrote: > @paulmenzel is there any possibilty we can get remote access to a > ppc64le in case we can't reproduce it on our platforms? Yes,...

On 12/05/18 15:46, Jörg Winkler wrote: > I actually have an account in the MPI-MG; I just need the host name > of a ppc64le machine where I can log...

On 12/10/18 13:01, Jörg Winkler wrote: > Also in version d7b7124d7 multiple tests fail (in Debug mode only). Thank you for looking into that. > @paulmenzel Which compiler flags do...

Didn’t you write, that tests failed for you too? Anyway, building in my home directory, tests still fail, but unfortunately not reproducibly. $ make test […] The following tests FAILED:...

Not for merge! Just to debug issue #213.

I’d squash the second into the first commit, but besides that, that’s also what I need for my environment.

It looks like IBM already ported Bowtie 2, at least the folks from [BioBuilds](https://biobuilds.org/) [carry patches](https://biobuilds.org/tools-in-biobuilds/biobuilds-2016-11/). Coordination on how to get this upstream, is appreciated.

This tries to address issues https://github.com/NLnetLabs/unbound/issues/475 and https://github.com/NLnetLabs/unbound/issues/476, but it’s incomplete. See the issues for discussion.

@Maryse47, @hardfalcon, it’d be great if you shared your expertise.