"bzero" should be avoided for maximum portability. Just use "memset" instead.
Even older versions of GCC know how to spot the 0 constant and substitute the
right compiler intrinsic(s), assuming they are available for the target
platform.
http://pubs.opengroup.org/onlinepubs/009695399/function
Can you please do a "man bzero" and tell us what include file it says we need?
On Sep 19, 2013, at 3:33 AM, Siegmar Gross
wrote:
> Hello Josh,
>
> I just tried to compile openmpi-1.9a1r29209 with gcc-4.8.0 and get the
> following error on Solaris sparc and Solars x86_64.
>
> sunpc1 openmpi-1
Hello Josh,
I just tried to compile openmpi-1.9a1r29209 with gcc-4.8.0 and get the
following error on Solaris sparc and Solars x86_64.
sunpc1 openmpi-1.9a1r29209-SunOS.x86_64.64_gcc 24 tail -14
log.make.SunOS.x86_64.64_gcc
make[2]: Entering directory
`/export2/src/openmpi-1.9/openmpi-1.9a1r292
Hello Josh,
> Try now, please.
I can build openmpi-1.9a1r29209 with my Sun C compiler on my platforms.
Thank you very much for your help! I can even use it on Linux and
I still get a Bus Error on Solaris, but that is a different problem.
I'm happy that I have at least one working platform again.
Siegmar,
Try now, please.
Best,
Josh
-Original Message-
From: Siegmar Gross [mailto:siegmar.gr...@informatik.hs-fulda.de]
Sent: Wednesday, September 18, 2013 6:32 AM
To: de...@open-mpi.org
Cc: siegmar.gr...@informatik.hs-fulda.de; Joshua Ladd
Subject: RE: [OMPI users] Error in openmpi-
Hello Josh,
thank you very much for your help. Unfortunately I have still a
problem to build Open MPI.
> I pushed a bunch of fixes, can you please try now.
I tried to build /openmpi-1.9a1r29197 on my platforms and now I get
on all platforms the following error.
linpc1 openmpi-1.9a1r29197-Linux
Siegmar,
I pushed a bunch of fixes, can you please try now.
Best,
Josh
-Original Message-
From: Jeff Squyres (jsquyres) [mailto:jsquy...@cisco.com]
Sent: Tuesday, September 17, 2013 6:37 AM
To: Siegmar Gross; Open MPI Developers List
Cc: Joshua Ladd
Subject: Re: [OMPI users] Error in o
...moving over to the devel list...
Dave and I looked at this during a break in the EuroMPI conference, and noticed
several things:
1. Some of the shmem interfaces are functions (i.e., return non-void) and some
are subroutines (i.e., return void). They're currently all using a single
macro to
