Many thanks for all the people giving me advices.
I have solved the problem. As most of them suggested, the problem was
incompatibility in the created objects between gcc and ifort.
I do not have icc, and hence use gcc right now. In this case, by
simply including options
CFLAGS=-m64 CXXFLA
How about a compromise -- I'll extend the message to also include the
possibility of architecture mismatches.
On Apr 24, 2008, at 1:12 PM, Doug Reeder wrote:
Jeff,
I don't know if it there is a way to capture the "not of required
architecture" response and add it to the error message. I agre
On Apr 25, 2008, at 1:24 AM, Koun SHIRAI wrote:
I understand that it is difficult to fully describe practical
notifications for each implementation, because of a lots of OS's and
its frequent revisions. In spite of this difficulty, I am wondering
why typical examples for configure are not given
Sorry, I should have been more specific: how about this?
**
It appears that your Fortran 77 compiler is unable to link against
object files created by your C compiler. This typically indicates
one of a few possibilities:
- A
Dear Jeff:
Of course, we don't want as many as parameters. Simply command lines
are absolutely better. But, it is impossible owing to complicated
systems. This is why you supply a lot of option commands.
I think that for most of beginners installation is a big barrier. If
in this stage
On Apr 25, 2008, at 7:33 AM, Koun SHIRAI wrote:
Of course, we don't want as many as parameters. Simply command lines
are absolutely better. But, it is impossible owing to complicated
systems. This is why you supply a lot of option commands.
I think that for most of beginners installation is a
Hi Jeff,
> >> All you need to do is install them both into separate prefixes
> >> (e.g., /
> >> opt/openmpi and /opt/mpich). Then when you're using them, ensure
> >> that
> >> your PATH / LD_LIBRARY_PATH is set consistently across all nodes, or
> >> if using Open MPI, use the options listed i
On Apr 25, 2008, at 10:54 AM, Hans Wurst wrote:
So you'll need to
compile your benchmarks for each MPI implementation that you want to
test (i.e., use that MPI's wrapper compilers to compile them).
I'm not conscious about what a MPI wrapper compiler is and how it
works.
mpicc (et al.) are
Jeff,
I think that error message is a good compromise and addresses the
most common problems that cause it to be written.
Doug Reeder
On Apr 25, 2008, at 4:08 AM, Jeff Squyres wrote:
Sorry, I should have been more specific: how about this?
**
Using the modules software (modules.sourceforge.net) works pretty
well for managing multiple mpi flavors. You still need to put each
mpi flavor's bin, lib, and include files in uniquely named paths,
then modules lets you put the appropriate mpi flavor in your path for
each application. It t
Slightly off topic but hopefully useful...
Just a little bit of trivia with the Intel Compilers on Mac OS X. One
of the nuances about the Intel compilers, unlike GCC, are that they
are two different compilers, a 64-bit compiler and a 32-bit compiler.
The 64-bit compilers are installed under
On Apr 24, 2008, at 10:48 AM, Jeff Squyres (jsquyres) wrote:
You probably want to use all the intel compilers, not just ifort.
CC=icc
CXX=icpc
FC=ifort
F77=ifort
I have long used gcc and ifort on 64-bit Linux (since SUSE did 64-bit
Linux on AMD Opterons), I don't see a good reason why OS X
Hello
As a newcomer to the world of openMPI who has perused the faq and
searched
the archives, I have a few questions about how to schedule processes
across
a heterogeneous cluster where some processes must be bound to particular
nodes and where some processes will not be compute bound, mea
OK folks,
Whilst testing cases of ratcheting up memory usage under Mac OSX
Leopard I ran into a peculiar problem of segmentation faults that just
should not be happening. I whittled down the code to find where the
error took place and well, for this simple code...
#include
#include
int
On Apr 25, 2008, at 2:06 PM, Gregory John Orris wrote:
produces a core dump on a machine with 12Gb of RAM.
and the error message
mpiexec noticed that job rank 0 with PID 75545 on node mymachine.com
exited on signal 4 (Illegal instruction).
However, substituting in
float *X = new float[n];
fo
Is it considered a feature that mpicc does not automatically link
against the Fortran libraries?
When I have a C main that uses a few Fortran functions down in the
guts I like to link with the
C linker, but mpicc does not appear to automatically link against
the Fortran libraries (mp
On Apr 25, 2008, at 4:10 PM, Brian Barrett wrote:
On Apr 25, 2008, at 2:06 PM, Gregory John Orris wrote:
produces a core dump on a machine with 12Gb of RAM.
and the error message
mpiexec noticed that job rank 0 with PID 75545 on node mymachine.com
exited on signal 4 (Illegal instruction).
This has nothing to do with the segmentation fault you got but in addition to
Brian comment, I would suggest you to not forget that with ISO C++ (the C++98
standard and the upcoming C++0x) a constant expression known at compile time is
needed for dimensions of local arrays.
In other words, a co
Brian,
Thanks, and my apologies.
This is an issue once known to me on an old CRAY/SGI, but lost in the
mists of time (>10 years). Stack size increase did the trick. Of
course putting everything on the heap via new and malloc would work
for arrays, but that creates such an inelegant looking c
I believe that you can also add this to your LIB or LDFLAGS for 64-bit
applications:
-Wl,-stack_addr,0xF1000 -Wl,-stack_size,0x6400
Warner Yuen
Scientific Computing
Consulting Engineer
Apple Computer
email: wy...@apple.com
Tel: 408.718.2859
Fax: 408.715.0133
On Apr 25, 2008, at 1:1
Josh,
I'm responding to some outstanding questions about the env. I'm trying to
ompi-restart in.
My answers to your questions are sprinkled below, and include a few more
questions based on attempts I've made to get a multi-node restart working.
thanks,
Sharon
Sharon Brunett wrote:
Josh Hursey
A smarter colleague then I, has reminded me that is very difficult
to obtain all the
Fortran libraries and linker options that would be needed to allow the
mpicc compiler to
also link against the MPI fortran libraries successfully. I therefor
withdraw my
original question?
Barry
On 25 April 2008 at 20:10, Barry Smith wrote:
|
|
| A smarter colleague then I, has reminded me that is very difficult
| to obtain all the
| Fortran libraries and linker options that would be needed to allow the
| mpicc compiler to
| also link against the MPI fortran libraries successful
23 matches
Mail list logo
