When you do a make can your add a V=1 to have the actual compile lines
printed out. That will probably show you the line with
-fno-directives-only in it. Which is odd because I think that option is
a gcc'ism and don't know why it would show up in a studio build (note my
build doesn't show it
On 10/21/2010 10:18 AM, Jeff Squyres wrote:
Terry --
Can you file relevant ticket(s) for v1.5 on Trac?
Once I have more information and have proven it isn't due to us using
old compilers or a compiler error itself.
--td
On Oct 21, 2010, at 10:10 AM, Terry Dontje wrote:
I've reproduced Si
> I wonder if the error below be due to crap being left over in the
> source tree. Can you do a "make clean". Note on a new checkout from
> the v1.5 svn branch I was able to build 64 bit with the following
> configure line:
linpc4 openmpi-1.5-Linux.x86_64.32_cc 123 make clean
Making clean i
Terry --
Can you file relevant ticket(s) for v1.5 on Trac?
On Oct 21, 2010, at 10:10 AM, Terry Dontje wrote:
> I've reproduced Siegmar's issue when I have the threads options on but it
> does not show up when they are off. It is actually segv'ing in
> mca_btl_sm_component_close on an access
I've reproduced Siegmar's issue when I have the threads options on but
it does not show up when they are off. It is actually segv'ing in
mca_btl_sm_component_close on an access at address 0 (obviously not a
good thing). I am going compile things with debug on and see if I can
track this furt
On 10/21/2010 06:43 AM, Jeff Squyres (jsquyres) wrote:
Also, i'm not entirely sure what all the commands are that you are
showing. Some of those warnings (eg in config.log) are normal.
The 32 bit test failure is not, though. Terry - any idea there?
The test program is failing in MPI_Finalize w
Also, i'm not entirely sure what all the commands are that you are showing.
Some of those warnings (eg in config.log) are normal.
The 32 bit test failure is not, though. Terry - any idea there?
Sent from my PDA. No type good.
On Oct 21, 2010, at 6:25 AM, "Terry Dontje" wrote:
> I wonder if
I wonder if the error below be due to crap being left over in the
source tree. Can you do a "make clean". Note on a new checkout from
the v1.5 svn branch I was able to build 64 bit with the following
configure line:
../configure FC=f95 F77=f77 CC=cc CXX=CC --without-openib
--without-udapl
Hi,
thank you very much for your reply.
> Can you remove the -with-threads and -enable-mpi-threads options from
> the configure line and see if that helps your 32 bit problem any?
I cannot build the package when I remove these options.
linpc4 openmpi-1.5-Linux.x86_64.32_cc 189 head -8 config
Can you remove the -with-threads and -enable-mpi-threads options from
the configure line and see if that helps your 32 bit problem any?
--td
On 10/20/2010 09:38 AM, Siegmar Gross wrote:
Hi,
I have built Open MPI 1.5 on Linux x86_64 with the Oracle/Sun Studio C
compiler. Unfortunately "mpiexec
Just to be clear: it isn't mpiexec that is failing. It is your MPI application
processes that are failing.
On Oct 20, 2010, at 7:38 AM, Siegmar Gross wrote:
> Hi,
>
> I have built Open MPI 1.5 on Linux x86_64 with the Oracle/Sun Studio C
> compiler. Unfortunately "mpiexec" breaks when I run a
Hi,
I have built Open MPI 1.5 on Linux x86_64 with the Oracle/Sun Studio C
compiler. Unfortunately "mpiexec" breaks when I run a small propgram.
linpc4 small_prog 106 cc -V
cc: Sun C 5.10 Linux_i386 2009/06/03
usage: cc [ options] files. Use 'cc -flags' for details
linpc4 small_prog 107 uname -
12 matches
Mail list logo
