Okay, some things I am already discovering. If you do an "svn up", there is 
some file cleanup you'll need to do to get this to build again. Specifically, 
you need to:

rm config/mca_m4_config_include.m4

as this is a stale file that will linger and screw things up.


On Sep 17, 2010, at 4:57 PM, Ralph Castain wrote:

> After chatting with Jeff, we decided it would be good to introduce this into 
> the trunk over the weekend so it can settle before people started beating on 
> it. Please note:
> 
> WARNING: Work on the temp branch being merged here encountered problems with 
> bugs in subversion. Considerable effort has gone into validating the branch. 
> However, not all conditions can be checked, so users are cautioned that it 
> may be advisable to not update from the trunk for a few days to allow MTT to 
> identify platform-specific issues.
> 
> See Jeff's notes below about THINGS YOU NEED TO KNOW.
> 
> Ralph
> 
> On Sep 15, 2010, at 12:34 PM, Jeff Squyres wrote:
> 
>> Ya, timezone differences and limited communication make it hard / make 
>> miscommunication easy.
>> 
>> We're not going to wait a year.  We're not going to wait a month.  
>> 
>> Ralph and I just need to sync up and get this stuff in.  I'm *guessing* 
>> it'll be ready in a week or so.  I'll be on the call to discuss next Tuesday.
>> 
>> 
>> On Sep 13, 2010, at 3:49 PM, Ralph Castain wrote:
>> 
>>> Just to correct: I will almost certainly not be on this week's call, and 
>>> will definitely not be on for the next two weeks either.
>>> 
>>> A last-minute concern raised by Jeff makes it doubtful this will come into 
>>> the trunk any time soon, and may see it delayed for more than a year until 
>>> we are ready for a 1.7 series. Unclear at this time as I don't understand 
>>> the nature of his concern, and communication is difficult across the globe.
>>> 
>>> For now, we can safely table this issue. It isn't coming in anytime soon.
>>> 
>>> 
>>> On Sep 12, 2010, at 2:40 AM, Jeff Squyres wrote:
>>> 
>>>> (Terry: please add this to the agenda for the Tuesday call -- Ralph will 
>>>> talk about it since I may not be on the call)
>>>> 
>>>> Ralph sent a mail a while ago describing improvements to autogen and the 
>>>> build process that Brian, Ralph, and I have been working on.  We think 
>>>> this work is now complete, and would like to bring it back to the SVN 
>>>> trunk.  Here's the bitbucket where this stuff lives:
>>>> 
>>>> http://bitbucket.org/rhc/ompi-agen
>>>> 
>>>> We'd like to bring this stuff in to the SVN trunk by the end of the week.  
>>>> Please examine our changes and/or test the things you care about in the 
>>>> bitbucket.  The SVN commit to the trunk will look large mainly because it 
>>>> makes almost-identical changes in many Makefile.am's and configure.m4's 
>>>> (and we removed all configure.params files).
>>>> 
>>>> ********************************************************
>>>> *** 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.  We'll update the relevant wiki pages with all the other 
>>>> details:
>>>> 
>>>> 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
>>>> 
>>>> We understand that Mellanox may have some changes to their local branch of 
>>>> the OMPI build system; it is unknown whether they conflict with our new 
>>>> stuff or not.  Mellanox is out for ~2 weeks for holidays; we'd like to 
>>>> bring this stuff in to the SVN trunk sooner rather than waiting 2 weeks 
>>>> and letting the branch get overly stale.  Of course, when Mellanox does 
>>>> update and get the new stuff, if there are any problems, I'm happy to work 
>>>> through the issues with them.
>>>> 
>>>> -- 
>>>> 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
>>> 
>>> 
>>> _______________________________________________
>>> devel mailing list
>>> de...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> 
>> 
>> -- 
>> 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