Summary: | dev-util/valgrind-3.4.0 should support IUSE=mpi | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Max <iprmaster> |
Component: | New packages | Assignee: | Maurice van der Pot (RETIRED) <griffon26> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | alexxy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 258964 | ||
Bug Blocks: |
Description
Max
2009-02-13 09:53:33 UTC
The reason this was added is bug #202684. Valgrind's upstream has explained what's going on in http://bugs.kde.org/show_bug.cgi?id=154240. I added a bug to bugzilla for the root cause. Once that has been solved, I can fix this one. (In reply to comment #1) > The reason this was added is bug #202684. Valgrind's upstream has explained > what's going on in http://bugs.kde.org/show_bug.cgi?id=154240. > > I added a bug to bugzilla for the root cause. Once that has been solved, I can > fix this one. > I see, but I think it is a matter of which mpi-implementation is provided. On my PC the sys-cluster/mpich2/mpich2-1.0.3 ebuild is installed, and I can compile valgrind by the following steps: 1- (like in the bug description) 2- (like in the bug description) 3- cd /var/tmp/portage/dev-util/valgrind-3.4.0/work/valgrind-3.4.0 4- ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-x --build=i686-pc-linux-gnu (actually these are the original ebuild-options, except for the missing --without-mpicc) 5- make && make install and everything works fine. Would be possible to introduce a configure-dependence of the mpi flag on the installed mpi-version? Thanks & regards, Max I just added valgrind-3.4.1-r1, which supports the mpi use flag. Thanks. |