I'm unable to reproduce your error, even with a git clone of the mirror.  
Perhaps you need to "git clean -df"?


On May 8, 2014, at 9:09 AM, Ashley Pittman <ash...@pittman.co.uk> wrote:

> 
> I started getting build failures against trunk on the 29th, most likely as a 
> result of this commit:
> 
> https://github.com/open-mpi/ompi-svn-mirror/commit/3f42cbf50670c5b311cc4414dbb3f4ccf762e455
> 
> It looks like there was another commit almost immediately afterwards which 
> fixed the first problem (include file errors) however I’m still seeing build 
> failures with the following error, I don’t know if this is still aside effect 
> of the previous VPATH problem or something else.
> 
> Making all in mpi
> make[10]: Entering directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/extlib/otf/tools/otfmerge/mpi'
> ln -s 
> ../../../../../../../../../../source/ompi/contrib/vt/vt/extlib/otf/tools/otfmerge/handler.c
>  handler.c
>  CC       otfmerge_mpi-handler.o
> ln -s 
> ../../../../../../../../../../source/ompi/contrib/vt/vt/extlib/otf/tools/otfmerge/otfmerge.c
>  otfmerge.c
>  CC       otfmerge_mpi-otfmerge.o
>  CCLD     otfmerge-mpi
> /space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/../../../.libs/libmpi.so:
>  undefined reference to `opal_dstore_peer'
> /space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/../../../.libs/libmpi.so:
>  undefined reference to `opal_value_load'
> /space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/../../../.libs/libmpi.so:
>  undefined reference to `opal_value_unload'
> /space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/../../../.libs/libmpi.so:
>  undefined reference to `opal_dstore_nonpeer'
> /space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/../../../.libs/libmpi.so:
>  undefined reference to `opal_dstore_internal'
> /space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/../../../.libs/libmpi.so:
>  undefined reference to `opal_dstore'
> collect2: error: ld returned 1 exit status
> make[10]: *** [otfmerge-mpi] Error 1
> make[10]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/extlib/otf/tools/otfmerge/mpi'
> make[9]: *** [all-recursive] Error 1
> make[9]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/extlib/otf/tools/otfmerge'
> make[8]: *** [all-recursive] Error 1
> make[8]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/extlib/otf/tools'
> make[7]: *** [all-recursive] Error 1
> make[7]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/extlib/otf'
> make[6]: *** [all] Error 2
> make[6]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/extlib/otf'
> make[5]: *** [all-recursive] Error 1
> make[5]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt/extlib'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt/vt'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory 
> `/space/jenkins/workspace/open-mpi/build/ompi/contrib/vt'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/space/jenkins/workspace/open-mpi/build/ompi'
> make: *** [all-recursive] Error 1
> 
> 
> The build script I’m using is fairly simple, it’s working from a clean 
> checkout each time but is doing a “VPATH” or out-of-tree build
> 
> cd source
> ./autogen.sh
> cd ..
> [ -d build ] && rm -rf build
> [ -d build ] && rm -rf install
> mkdir build
> cd build
> ../source/configure --enable-mpirun-prefix-by-default --prefix 
> $WORKSPACE/install
> make
> make install
> 
> Ashley,
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/05/14753.php


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

Reply via email to