Thanks for your suggestions.
Jeff Squyres wrote:
> From the stack trace, it looks like you're in the middle of a
> complex deallocation of some C++ objects, so I really can't tell
> (i.e., not in an MPI function at all).
Well, not intentionally! I'm just calling "deallocate" in a purely
Fortra
I'm not entirely sure what the problem is with the
--with/--without flags. Within the configure script,
these flags enable/disable the setting of certain
environment variables and/or the running of certain
tests.
Within the RPM spec file, these need to be given,
sure, but in many cases there will
Confirmed by author of g95:
On Jan 26, 2006, at 3:40 PM, Andy Vaught wrote:
It's a known issue. Use
LDFLAGS=-lSystemStubs
on the configure line.
On Jan 26, 2006, at 11:35 AM, Kraig Winters wrote:
I believe that
ld: Undefined symbols:
_fprintf$LDBLStub
can be fixed by adding -L/usr/lib
I believe that
ld: Undefined symbols:
_fprintf$LDBLStub
can be fixed by adding -L/usr/lib -lSystemStubs to your link statement.
For xlf, this can be done once and for all in the compiler configuration
file. I don't know if something similar can be done for g95. This
problem
seems to have star
This looks like a problem with the memory allocator. It could be a
genuine problem with Open MPI, or it could be a memory fault in your
application (that happens to dead-end in one of our libraries because
we intercept memory allocation functions). From the stack trace, it
looks like you'
On Jan 25, 2006, at 6:32 PM, Daryl W. Grunau wrote:
Is there a more scalable way to do this, perchance?
I was trying to make the option-generator into a function which
could be
called in the %description section or in the %configure line so you'd
only need to maintain one area. I haven't f
It looks like your g95 may not be installed correctly. Here's the
relevant information from the config.log:
configure:32697: gcc -O3 -DNDEBUG -fno-strict-aliasing -I. -c conftest.c
configure:32704: $? = 0
configure:32714: g95 conftestf.f90 conftest.o -o conftest
ld: Undefined symbols:
_fprin
