The tarball got mucked up last night due to a minor ROMIO file permission
problem; let's see what happens tonight.
On Jan 19, 2011, at 8:36 PM, Terry Dontje wrote:
> Hopefully we'll find out tomorrow but I think I vaguely remember an issue
> with the Studio compilers and this type of initializ
On Jan 19, 2011, at 19:39 , Jeff Squyres (jsquyres) wrote:
> I'd rather not setup another SVN repo. Where should it go in the current OMPI
> SVN?
contrib?
george.
>
> Sent from my PDA. No type good.
>
> On Jan 19, 2011, at 5:01 PM, "George Bosilca" wrote:
>
>>
>> On Jan 19, 2011, at 1
This may be a good candidate for: svn-root/tmp-public/
On Jan 20, 2011, at 12:42 PM, George Bosilca wrote:
>
> On Jan 19, 2011, at 19:39 , Jeff Squyres (jsquyres) wrote:
>
>> I'd rather not setup another SVN repo. Where should it go in the current
>> OMPI SVN?
>
> contrib?
>
> george.
>
>>
Hmm. I'm not sure I like either suggestion. :-\
1. contrib: the problem with this is that there are 3 modules in here: trunk,
v1.4, and v1.5. Should I put this in the contrib on each branch? Hmm. But
then again, it won't be distributed as part of Open MPI, so technically it
wouldn't violate
Even before getting into the Oracle compiler, a fully compliant C99 compiler
such as gcc 4.2.1 complains a lot about the new code. Here is what I get:
../../../../../ompi/orte/mca/debugger/dummy/dummy_component.c:25: warning: ISO
C90 forbids specifying subobject to initialize
../../../../../ompi
same type of warnings with gcc-4.3.3
george.
On Jan 20, 2011, at 15:21 , George Bosilca wrote:
> Even before getting into the Oracle compiler, a fully compliant C99 compiler
> such as gcc 4.2.1 complains a lot about the new code. Here is what I get:
>
> ../../../../../ompi/orte/mca/debugger/
I didn't see those warning on my mac when I compiled but gcc does indeed
complain if -pedantic is specified without the -std=c99 option. So, in order to
use the initialization style we would need to specify -std=c99 option for gcc.
Not sure if there would be a problem specifying -std=c99?
-Nat
This is because gcc is defaulting to -std=c90. I strongly suspect that
adding -std=c99 to the CFLAGS eliminates George's warnings. However,
one may need to hunt down equivalent dialect flags for other compilers too.
-Paul
George Bosilca wrote:
same type of warnings with gcc-4.3.3
george.
Hello,
I'm trying to build OpenMPI with fortran on my Mac OS machines using gfortran.
I'm using the 64-bit option and trying to install 1.4.2. It seems to build ok
and when I compile and run simple programs it works. When I try a more
complicated case it works on my desktop but not my laptop
Yeah, it seems that if the standard is not specified gcc backs off to gnu89
(c90 + some of c99). I have tested the following compilers so far:
gcc : ok by default, not ok with -pedantic unless -std=c99 is specified
icc : ok without any flags, strangely ok with -no-c99 (probably
su
Francis,
I cannot address your situation specifically, but I can tell you from
experience that you must pay close attention to the version of Mac OS
X for 32-bit/64-bit compiling. gcc/gfortran defaults to 32-bit on OS
X 10.5. I am told they default to 64-bit on OS X 10.6. Thus, to
comp
11 matches
Mail list logo
