[petsc-dev] Error while building MAGMA from PETSc

Harshad Sahasrabudhe hsahasra at purdue.edu
Thu Aug 15 14:43:46 CDT 2013


Attached is the diff and configure.log

----- Original Message -----
From: "Jed Brown" <jedbrown at mcs.anl.gov>
To: "Matthew Knepley" <knepley at gmail.com>
Cc: "Harshad Sahasrabudhe" <hsahasra at purdue.edu>, "For users of the development version of PETSc" <petsc-dev at mcs.anl.gov>
Sent: Thursday, August 15, 2013 3:33:33 PM
Subject: Re: [petsc-dev] Error while building MAGMA from PETSc



... and send the changes you have made. One way to do that is to 'git add config/PETSc/packages/magma.py' and send the output if 'git diff master'. 
On Aug 15, 2013 2:28 PM, "Matthew Knepley" < knepley at gmail.com > wrote: 



On Thu, Aug 15, 2013 at 1:56 PM, Harshad Sahasrabudhe < hsahasra at purdue.edu > wrote: 




Hi, 

Now MAGMA compiles correctly and libmagma.a is generated, however PETSc says 

Downloaded magma could not be used. Please check install in /home/harshad/workspace/petsc-hg/arch-linux2-c-debug 

I am copying the generated library and include files to the install directory using 

includeDir = os.path.join(self.installDir, self.includedir) 
output,err,ret = PETSc.package.NewPackage.executeShellCommand('cd '+self.packageDir+' && mv -f lib/*.* '+libDir+'/. && cp -f include/*.* '+includeDir+'/.', timeout=2500, log = self.framework.log) 

I need help in resolving this error. 



Always send configure.log. 


Matt 


Thanks, 
Harshad 

----- Original Message ----- 
From: "Matthew Knepley" < knepley at gmail.com > 
To: "Harshad Sahasrabudhe" < hsahasra at purdue.edu > 
Cc: "For users of the development version of PETSc" < petsc-dev at mcs.anl.gov > 
Sent: Wednesday, August 14, 2013 6:27:04 PM 
Subject: Re: [petsc-dev] Error while building MAGMA from PETSc 


On Wed, Aug 14, 2013 at 5:23 PM, Harshad Sahasrabudhe < hsahasra at purdue.edu > wrote: 






Hi, 

I'm trying the write the package compiler for MAGMA using PETSc build system. I'm getting the following error while building MAGMA. With the error, I'm also getting a couple hundred warnings: 

sormqr_gpu_2stage.cpp: In function ‘magma_int_t magma_sormqr_gpu_2stages(char, char, magma_int_t, magma_int_t, magma_int_t, float*, magma_int_t, float*, magma_int_t, float*, magma_int_t, magma_int_t*)’: 
sormqr_gpu_2stage.cpp:98: warning: unused variable ‘c_one’ 
sormqr_gpu_2stage.cpp:107: warning: unused variable ‘lwkopt’ 
strsm_m.cpp: In function ‘magma_int_t magma_strsm_m(magma_int_t, char, char, char, char, magma_int_t, magma_int_t, float, float*, magma_int_t, float*, magma_int_t)’: 
strsm_m.cpp:181: warning: unused variable ‘jj’ 
strsm_m.cpp:181: warning: unused variable ‘jjb’ 
sgeev.cpp: In function ‘magma_int_t magma_sgeev(char, char, magma_int_t, float*, magma_int_t, float*, float*, float*, magma_int_t, float*, magma_int_t, float*, magma_int_t, magma_int_t*)’: 
sgeev.cpp:126: warning: unused variable ‘c_n1’ 
nvcc fatal : redefinition of argument 'gpu-architecture' 


What is the easiest way to debug this kind of an error? 



1) Make the MAGMA build system print out the full compile line 


2) Make the MAGMA people clean up their sloppy code, which would eliminate the warnings 


Matt 




Thanks, 
Harshad 





-- 
What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. 
-- Norbert Wiener 




-- 
What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. 
-- Norbert Wiener
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff_magma
Type: text/x-patch
Size: 4748 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130815/c56f9b51/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.log
Type: text/x-log
Size: 2779222 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130815/c56f9b51/attachment-0001.bin>


More information about the petsc-dev mailing list