make test seems to be hanging with these changes, whereas it runs in just 1 second without including jemalloc as a dep, interesting...

@boegel I confirm that the test hangs with jemalloc.

Which version of jemalloc does it ship with?

@wpoely86 Same version as the one I'm using here. Which makes it even weirder. Maybe they do something special that doesn't happen if an external jemalloc is used. Or maybe it's the $LD_PRELOAD we do in jemalloc?

Unsetting $LD_PRELOAD before make test fixes the issue for me, but then I wonder what effect it's have on Salmon itself outside of the tests...

but how does it use jemalloc then?

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2402.golett.os - Linux centos linux 7.6.1810, Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, Python 2.7.5
See https://gist.github.com/78946bb19ac5946987267379c583f4d8 for a full test report.

@wpoely86 Salmon statically links in jemalloc, so just a build dep is sufficient (changed in b95f313).

I've retested the resulting salmon binary using the examples explained in https://combine-lab.github.io/salmon/getting_started/, works fine, so this is good to go imho...

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2727.swalot.os - Linux centos linux 7.6.1810, Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz, Python 2.7.5
See https://gist.github.com/7b8afabfde988cc5fab120e8b5335314 for a full test report.

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node3122.skitty.os - Linux centos linux 7.6.1810, Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz, Python 2.7.5
See https://gist.github.com/7462f47e66688b5091eda5914576dfd7 for a full test report.

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2006.delcatty.os - Linux centos linux 7.6.1810, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.7.5
See https://gist.github.com/7eff773ebe259a2ff36755826c785620 for a full test report.