On 21.04.2011, at 20:28, Derek Gaston wrote:
> On Apr 21, 2011, at 10:32 AM, John Peterson wrote:
>
>> So, looks like you didn't download BLAS/Lapack through PETSc, and
>> therefore it must be finding and using some other BLAS on your system,
>> possibly C BLAS since you specified --with-fc=0?
>
> If you haven't recompiled Petsc since you switched compilers that could
> easily be a source of this problem. I would suggest that you make sure that
> your HPC compilers are completely removed and that all of your various search
> paths have been sanitized of those paths before reconfigurin
> It looks like you have some issues with your underlying BLAS and Lapack
> libraries. How are you configuring Petsc and what compilers are you using?
> Are you using the Apple supplied compilers and MPICH wrappers or did you
> build any of that on your own?
>
Yes, I use the Apple compilers
Yes, all PETSc and SLEPc tests succeed, and also all the other libMesh examples
(apart from 16, 17) work fine.
My own applications using SLEPc fail, too.
-Anna
On 21.04.2011, at 11:44, Roy Stogner wrote:
>
> On Thu, 21 Apr 2011, Anna-Lena Gerner wrote:
>
>> All of a sudden
Hi everyone,
All of a sudden, I receive the following runtime-error whenever an application
uses slepc:
dyld: lazy symbol binding failed: Symbol not found: _dhseqr
Referenced from: /home/gerner/Software/libmesh/examples/ex16/./ex16-dbg
Expected in: flat namespace
dyld: Symbol not found: _d
he exception of the sharedlibs. My path is
> correct to pick up the HPC version of the GCC compilers NOT THE APPLE
> versions. Finally all the extra flags are there to make sure I don't put any
> flags into wrappers but that I can still compile the library itself in
> optimize
> In that case, would you try using a custom compilation method? Try
> building (after a clean) in devel mode, but with a CXXFLAGS
> environment variable set to include "-D_GLIBCXX_DEBUG
> -D_GLIBCXX_DEBUG_PEDANTIC"
>
> If that breaks, then it's probably some problem specific to your OS X
> GCC
On 10 Sep 2010, at 12:34, Roy Stogner wrote:
>
>
>>> On Sep 4, 2010, at 10:29 AM, Anna-Lena Gerner wrote:
>>>
>>>> I installed libMesh on my Mac OS X, and in opt mode everything is just
>>>> fine. There also seem to be no compilation problems i
On 7 Sep 2010, at 09:44, Cody Permann wrote:
>
> On Sep 4, 2010, at 10:29 AM, Anna-Lena Gerner wrote:
>
>>
>> Hi everybody,
>>
>> I installed libMesh on my Mac OS X, and in opt mode everything is just fine.
>> There also seem to be no compilatio
>
> Whenever I see a segfault coming from a weird place, in this case,
> from the destructor of std::string, I usually suspect an incomplete
> recompile of some sort. For example, object files from an older
> compiler version getting linked with object files from a new one, etc.
> Can you see if
Hi everybody,
I installed libMesh on my Mac OS X, and in opt mode everything is just fine.
There also seem to be no compilation problems in dbg mode. However, in dbg mode
I get the following runtime error: (./ex4-dbg -d 1 -n 20)
ex4-dbg(73819) malloc: *** error for object 0x1032e6fa0: pointer
Hi Roy,
Thank you so much for your help. I could not fix it, unfortunately, but since I
have switched to the compilers provided at http://hpc.sourceforge.net/ (as
Derek recommended), everything works fine.
Except there now appears an error when compiling ex17:
Compiling C++ (in optimized mode
On 10 Jun 2010, at 20:09, Roy Stogner wrote:
>
> On Thu, 10 Jun 2010, Anna-Lena Gerner wrote:
>
>> I am trying to install libmesh with petsc and openmpi on OS X 10.6.
>
> What underlying compilers are your mpicc and mpicxx using? A coworker
> here recently discovere
Hi all,
I am trying to install libmesh with petsc and openmpi on OS X 10.6.
libmesh configuration (exact petsc and libmesh configure options are given
below) and compilation worked fine but compiling the examples gives the warnings
ld: warning: directory
'-L/Users/agerner/Software/slepc-3.0.0
14 matches
Mail list logo
