We can build an SVN checkout, but with a tarball we get this:

  ...
  Undefined                     first referenced
   symbol                           in file
  opal_backtrace_print                ../../../opal/.libs/libopen-pal.so
  opal_backtrace_buffer               ../../../opal/.libs/libopen-pal.so
  ld: fatal: Symbol referencing errors. No output written to .libs/opal_wrapper

I suspect this is because the -G link lines for libopen-pal.so differ
between the tarball and the SVN checkout.  Specifically, this file
is *not* included in the link line in the tarball case:

  mca/backtrace/printstack/.libs/libmca_backtrace_printstack.a

I assume this means no backtrace plug-in is getting built in the
tarball case for some reason?

-Ethan

On Sat, Sep/18/2010 09:57:44AM, Jeff Squyres wrote:
> I made autogen.pl take care of removing stale generated-m4 files 
> automatically, so no one should need to manually rm any .m4 files.  Just 
> running autogen.pl should be sufficient.  Additionally, making nightly 
> tarballs was accidental collateral damage.  I'm working on fixing this; I 
> think I'm pretty close.
> 
> I updated the wiki pages last week with all you need to know about the 
> improvements to the build system:
> 
>     https://svn.open-mpi.org/trac/ompi/wiki/devel/Autogen
>     https://svn.open-mpi.org/trac/ompi/wiki/devel/CreateComponent
>     https://svn.open-mpi.org/trac/ompi/wiki/devel/CreateFramework
> 
> If you make any new components or frameworks, I highly suggest you re-read 
> these pages.
> 
> A note from a prior email is critically important for all developers:
> 
> >>>>> ********************************************************
> >>>>> *** THE MOST IMPORTANT THING DEVELOPERS NEED TO KNOW ***
> >>>>> ********************************************************
> >>>>> 
> >>>>> <IMPORTANT>
> >>>>> If your component has a configure.m4 file, it MUST call AC_CONFIG_FILES 
> >>>>> for your Makefile.am!  (and/or any files that you want configure to 
> >>>>> generate).  We converted all existing configure.m4 files -- the 
> >>>>> ompi/mca/btl/tcp/configure.m4 is a nice simple example to see what I 
> >>>>> mean.
> >>>>> </IMPORTANT>
> >>>>> 
> >>>>> There's some other changes and improvements, but most of them are 
> >>>>> behind the scenes.  
> 
> -- 
> 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

Reply via email to