Summary: | sci-biology/clustalw-mpi: ebuild requires lam-mpi although mpich2 is installed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | New packages | Assignee: | Gentoo Science Biology related packages <sci-biology> |
Status: | RESOLVED INVALID | ||
Severity: | trivial | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Mokrejš
2008-06-06 21:32:16 UTC
mpich2 is part of the mpi virtual and hence should be fine as a dependency of clustalw-mpi. However, since clustalw-mpi is only keyworded x86 you must have done something to the ebuild to be able to emerge it on amd64. Can you make sure you didn't accidentally change some dependencies and that your portage tree is up to date. Thanks, Markus Yes, I just unmasked clustalw-mpi with the hope I could compile and use it and report back. But I got stuck as I have reported. Ping. ;-) It seems the ebuild "as is" works also on ~amd64. Please add this arch to the list. I successfully compiled against mpich2-1.0.8-1. I definitely have no lam-mpi installed: # emerge -pv clustalw-mpi These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sci-biology/clustalw-mpi-0.13 USE="-mpi_njtree -static_pairalign" 0 kB # emerge -pv mpich2 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-cluster/mpich2-1.0.8-r1 USE="cxx -debug -doc -fortran -mpi-threads -pvfs2 -romio -threads" 0 kB [?=>1] Total: 1 package (1 reinstall), Size of downloads: 0 kB Portage tree and overlays: [0] /nfslarge/usr/portage [1] /nfslarge/usr/portage/local # Package correctly depends on virtual/mpi which is correct. Please open a new bug if you're requesting keywords. |