Re: [OMPI devel] oshmem 32 bit compile failures

2013-10-04 Thread Jeff Squyres (jsquyres)
On Oct 4, 2013, at 1:51 PM, Mike Dubman  wrote:

> the code passes compilation with gcc/icc 32bit toolkits.
> We don`t have absoft fortran compiler in the lab, is there any way we can 
> have it to try?

No -- Absoft themselves run the test and simply upload to our MTT (i.e., I 
don't have an Absoft license).

However, note that this problem is not in the Fortran code (Absoft is a 
Fortran-only compiler; it uses gcc/g++ for C/C++).  It says that it is using 
gcc 4.1.2.  Can you try a 32 bit build with gcc 4.1.x?

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/



Re: [OMPI devel] oshmem 32 bit compile failures

2013-10-04 Thread Mike Dubman
Hi,

the code passes compilation with gcc/icc 32bit toolkits.
We don`t have absoft fortran compiler in the lab, is there any way we can
have it to try?

Igor has some wild guess about what problem can be and created patch
(attached).
Could you try to apply it on OMPI tree and check with absoft compiler?

Thanks
M


On Fri, Oct 4, 2013 at 2:46 PM, Jeff Squyres (jsquyres)
wrote:

> Absoft is seeing compile failures for oshmem.  Here's one example:
>
> http://mtt.open-mpi.org/index.php?do_redir=2132
>
> If you scroll down through the stderr, it looks like there's a problem in
> oshmsm/op/op.c.  Perhaps it's just a missing header file, or some code in
> an #if/#else that isn't compiled/checked often...?
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>


2943-issue.patch
Description: Binary data


[OMPI devel] oshmem 32 bit compile failures

2013-10-04 Thread Jeff Squyres (jsquyres)
Absoft is seeing compile failures for oshmem.  Here's one example:

http://mtt.open-mpi.org/index.php?do_redir=2132

If you scroll down through the stderr, it looks like there's a problem in 
oshmsm/op/op.c.  Perhaps it's just a missing header file, or some code in an 
#if/#else that isn't compiled/checked often...?

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/