Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

It was a library from a colleague, particularly for internal use. So, this will not perpetuate to your users. I appreciate your concern and support. We will fix this at our end. -Manav > On Apr 8, 2017, at 11:28 PM, Barry Smith wrote: > > >> On Apr 8, 2017, at 11:21

Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

It turned out to be another third-party library that had some functions names same as those from BLAS. This was confusing LAPACK. Building without that library is leading to expected results from the code. What I don’t understand is why this shows up on one platform out of the four different

Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

I would do a minimal petsc build - without any packages from /usr/local - and see if the problem presists.. Satish On Fri, 7 Apr 2017, Barry Smith wrote: > > > On Apr 7, 2017, at 3:34 PM, Manav Bhatia wrote: > > > > Yes, I printed the data in both cases and they look

Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

> On Apr 7, 2017, at 3:34 PM, Manav Bhatia wrote: > > Yes, I printed the data in both cases and they look the same. > > I also used “set step-mode on” to show the system lapack info, and they both > are using the same lapack routine. > > This is still baffling me.

Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

Yes, I printed the data in both cases and they look the same. I also used “set step-mode on” to show the system lapack info, and they both are using the same lapack routine. This is still baffling me. -Manav > On Apr 7, 2017, at 3:22 PM, Barry Smith wrote: > > >> On

Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

> On Apr 7, 2017, at 2:57 PM, Manav Bhatia wrote: > > Hi Barry, > > Thanks for the inputs. > > I did try that, but the debugger (gdb) stepped right over the dgeev_ call, > without getting inside the function. Did it at least stop at the function so you do an up

Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

Hi Barry, Thanks for the inputs. I did try that, but the debugger (gdb) stepped right over the dgeev_ call, without getting inside the function. I am wondering if this has anything to do with the fact that the system lapack library might not have any debugging info in it.

Re: [petsc-users] odd behavior when using lapack's dgeev with petsc

> On Apr 7, 2017, at 1:46 PM, Manav Bhatia wrote: > > Hi, > >I have compile petsc on my Ubuntu machine (also Mac OS 10.12 separately) > to link to the system lapack and blas libraries (shown below). > >I have created an interface class to dgeev in lapack to