Hi Gilles There really isn't any need to open tickets when things like this happen. A simple note to devel is usually considered adequate. The problem will either be repaired by the responsible organization when they return to work, or we will revert the offending commit if the fix is going to take awhile.
The best solution in most cases is to simply roll your local repo back to a point before the offending commit until it gets fixed. These things happen, though not frequently. On Apr 14, 2014, at 8:03 PM, Gilles Gouaillardet <gilles.gouaillar...@iferc.org> wrote: > Folks, > > as reported in https://svn.open-mpi.org/trac/ompi/ticket/4521, configure > fails on the trunk :-( > > Dear OpenMPI Folks, > since r31390, configure fails on the trunk because oshmem/include/pshmem.h.in > in missing. > > i believe r31390 should have moved the profiling api from > oshmem/include/shmem.h.in into oshmem/include/pshmem.h.in. instead, r31390 > simply removed all the profiling api and did not include > oshmem/include/pshmem.h.in > > i am now trying to rebuild oshmem/include/pshmem.h.in in order to get things > work again > > Best regards, > > Gilles > > > _______________________________________________ > 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/04/14525.php
