Re: [Valgrind-users] Valgrind MPI fails to build libmpiwrapers

[janjust <tja...@un...>]

Hi Dave,
    Thank you so much for your help, that worked!
Much appreciated!
-Tommy


Bugzilla from go...@mc... wrote:
> 
> On Jun 28, 2011, at 3:45 PM CDT, Dave Goodell wrote:
> 
>> On Jun 28, 2011, at 2:56 PM CDT, janjust wrote:
>> 
>>>   Thanks for the reply. ; Setting $MPI_CC="mpicc -noswitcherror" moved
>>> the
>>> build a bit further but it exited with a different error, this time:
>>> 
>>> -------
> ...
>>> pgcc-Warning-Unknown switch: -fno-omit-frame-pointer
>>> pgcc-Warning-Unknown switch: -Wall
>>> pgcc-Warning-Unknown switch: -MT
>>> pgcc-Warning-Unknown switch: -MP
>>> pgcc-Warning-Unknown switch: -MF
>>> pgcc-Error-Output would overwrite input file:
>>> libmpiwrap_amd64_linux_so-libmpiwrap.o
>>> make[2]: *** [libmpiwrap_amd64_linux_so-libmpiwrap.o] Error 1
> ...
>>> ----------
>> 
>> Hmm... not sure why that's happening.  It looks like a bad makefile
>> recipe is getting generated somehow.  I'll poke at it when I get a little
>> more time.
> 
> Ahh, if I had just thought for a moment before firing off that last email
> I would have realized what happened in time.  Autoconf is probably
> detecting that your main compiler is gcc and using that.  So it sets some
> combination of automake conditionals to use gcc-style dependency tracking
> rules that are emitted inline into the Makefile.  However your mpicc is
> using a different compiler under the hood and pgcc doesn't understand the
> "-MT target" format, among other things.  So the dependency tracking rules
> that are used here are incorrect when compiling the MPI wrappers.
> 
> I suspect you can get past this particular error while still using the
> wrappers for pgcc by passing "--disable-dependency-tracking" to Valgrind's
> configure.  You may still want to pursue the GCC-based-MPI strategy for
> other reasons.
> 
> -Dave
> 
> 
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security 
> threats, fraudulent activity, and more. Splunk takes this data and makes 
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
> 
> 

-- 
View this message in context: http://old.nabble.com/Valgrind-MPI-fails-to-build-libmpiwrapers-tp31948567p31950666.html
Sent from the Valgrind - Users mailing list archive at Nabble.com.