John Peterson <jwpeter...@gmail.com> writes: > Ah, I'm using 3.3-p4, so that checkPESSL function looks for pdgemm in that > version:
Oh, now I remember that WTF moment.
commit 73dbc7173f5993ebbea13e62f9c58773df1a1b5b
Author: Jed Brown <j...@59a2.org>
Date: Sun Jan 20 13:09:14 2013 -0600
Detect PESSL using ipessl
Hg-commit: 890a4ed7f29bde8e40fec6dcfda01549a271a631
diff --git a/config/packages/BlasLapack.py b/config/packages/BlasLapack.py
index 8e27451..7e02b22 100644
--- a/config/packages/BlasLapack.py
+++ b/config/packages/BlasLapack.py
@@ -500,7 +500,7 @@ class Configure(config.package.Package):
def checkPESSL(self):
'''Check for the IBM PESSL library - and error out - if used instead of
ESSL'''
- if self.libraries.check(self.lapackLibrary, 'pdgemm'):
+ if self.libraries.check(self.lapackLibrary, 'ipessl'):
raise RuntimeError('Cannot use PESSL instead of ESSL!')
return
> I can definitely try using a newer PETSc if this turns out to be a
> show-stopper, but I don't think it will.
Well, we always recommend using the latest version of PETSc.
pgpyn_MuvGo0s.pgp
Description: PGP signature
------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
