Re: Parallel and MPI with default branch

[kingcrimson]

Hi,

I think I messed up esterday, it is not the linker but the compiler that is 
throwing out the error message.

It is a bit mess to reconstruct as you are doing a parallel build with 4 cores, 
but the exact error sequence
seems to be the following: 

> On 18 Feb 2018, at 17:56, Sebastian Schöps <address@hidden> wrote:
> 
> /usr/local/Cellar/octave/HEAD-90bd5649983c_1/bin/mkoctfile-4.3.0+ --verbose 
> -I/usr/local/Cellar/open-mpi/3.0.0_2/include -c MPI_Send.cc
> clang++ -std=gnu++11 -c -I/usr/X11/include -fPIC 
> -I/usr/local/Cellar/octave/HEAD-90bd5649983c_1/include/octave-4.3.0+/octave/..
>  -I/usr/local/Cellar/octave/HEAD-90bd5649983c_1/include/octave-4.3.0+/octave 
> -I/usr/local/Cellar/octave/HEAD-90bd5649983c_1/include  -D_THREAD_SAFE 
> -pthread -I/Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/include 
> -I/Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/include/darwin   
> -I/usr/local/Cellar/open-mpi/3.0.0_2/include  MPI_Send.cc -o MPI_Send.o

> MPI_Send.cc:90:26: error: no viable overloaded '='
>                  retval = info;
>                  ~~~~~~ ^ ~~~~
> /usr/local/Cellar/octave/HEAD-90bd5649983c_1/include/octave-4.3.0+/octave/ov.h:359:17:
>  note: candidate function not viable: no
>      known conversion from 'Array<int>' to 'const octave_value' for 1st 
> argument
>  octave_value& operator = (const octave_value& a)

The above sequence compares with the following commands that I see on my system 
(and without error):

/opt/octave/4.3.0+/bin/mkoctfile-4.3.0+ --verbose 
-I/opt/local/include/openmpi-mp -c MPI_Iprobe.cc
/usr/bin/clang++ -c -I/opt/local/include -I/opt/X11/include -fPIC 
-I/opt/octave/4.3.0+/include/octave-4.3.0+/octave/.. 
-I/opt/octave/4.3.0+/include/octave-4.3.0+/octave -I/opt/octave/4.3.0+/include  
-D_THREAD_SAFE -pthread -std=gnu++11   -I/opt/local/include/openmpi-mp  
MPI_Iprobe.cc -o MPI_Iprobe.o


The two look equivalent to me, do you see any relevant difference?

If not, the difference might be in the exact Octave release we are using, 
what does 

  __octave_config_info__ hg_id

return for you? For me it returns 

  >> __octave_config_info__ hg_id
  ans = 3da6c628873a

which refers to the following changeset:
  
  http://hg.savannah.gnu.org/hgweb/octave/rev/3da6c628873a

Hope this helps,
c.