Valgrind, an open-source memory debugger

> I just like to know whether it's possible to disable the MPI feature when building Valgrind.

Here are two things to try:

1) Uninstall MPI (at least 'mpicc') then re-build valgrind, starting with
   ./autogen.sh .  See "Building and installing it" in the README file.

or,
2) Remove the "mpi \" line from Makefile.am, then re-build valgrind,
   starting with  ./autogen.sh .

--

Thank you,

I removed mpi, build valgrind, and reinstall mpi.
It works.
Best,

                  Éric.

On 05/23/2011 10:36 PM, John Reiser wrote:
>> I just like to know whether it's possible to disable the MPI feature when building Valgrind.
> Here are two things to try:
>
> 1) Uninstall MPI (at least 'mpicc') then re-build valgrind, starting with
>     ./autogen.sh .  See "Building and installing it" in the README file.
>
> or,
> 2) Remove the "mpi \" line from Makefile.am, then re-build valgrind,
>     starting with  ./autogen.sh .
>

-- 
/Be the change you wish to see in the world
/ --- Mahatma Gandhi ---

One Human Family <http://onehumanfamily.info/>

/Please, if possible, don't send me MS Word or PowerPoint attachments
Why? See: http://www.gnu.org/philosophy/no-word-attachments.html /

On May 23, 2011, at 9:36 PM CDT, John Reiser wrote:

>> I just like to know whether it's possible to disable the MPI feature when building Valgrind.
> 
> Here are two things to try:
> 
> 1) Uninstall MPI (at least 'mpicc') then re-build valgrind, starting with
>   ./autogen.sh .  See "Building and installing it" in the README file.
> 
> or,
> 2) Remove the "mpi \" line from Makefile.am, then re-build valgrind,
>   starting with  ./autogen.sh .

Those are probably the most labor-intensive ways that you can do it.  It's usually easier to just pass "--without-mpicc" to configure and use the normal build process in all other respects.

-Dave

> Those are probably the most labor-intensive ways that you can do it.  It's usually easier to just pass "--without-mpicc" to configure and use the normal build process in all other respects.

1. No documentation: no mention of MPI in README*, no explicit list of packages
   that might be eligible for --without-*, etc.

2. The default "-with-mpicc" does not work (it fails to detect the unusable
   state on the original poster's machine), so the override "--without-mpicc"
   should be regarded with suspicion.

--

On May 24, 2011, at 12:02 PM CDT, John Reiser wrote:

>> Those are probably the most labor-intensive ways that you can do it.  It's usually easier to just pass "--without-mpicc" to configure and use the normal build process in all other respects.
> 
> 1. No documentation: no mention of MPI in README*, no explicit list of packages
>   that might be eligible for --without-*, etc.
> 
> 2. The default "-with-mpicc" does not work (it fails to detect the unusable
>   state on the original poster's machine), so the override "--without-mpicc"
>   should be regarded with suspicion.

I didn't mean it as any kind of personal slight, and I completely agree that this is both under-documented and slightly buggy.  I just wanted to get the easiest solution that I know actually works into the mail archives.

I've got ~1/2 of a patch to fix the mpicc detection already written that has been shelved for a while, perhaps I should resume work on it.  If I can get that working then none of these solutions should be necessary.

-Dave

On May 24, 2011, at 12:31 PM CDT, Dave Goodell wrote:

> I've got ~1/2 of a patch to fix the mpicc detection already written that has been shelved for a while, perhaps I should resume work on it.  If I can get that working then none of these solutions should be necessary.

FYI: https://bugs.kde.org/show_bug.cgi?id=274078

-Dave