1
1
Ralph Castain fceabb2498 Update libevent to the 2.0 series, currently at 2.0.7rc. We will update to their final release when it becomes available. Currently known errors exist in unused portions of the libevent code. This revision passes the IBM test suite on a Linux machine and on a standalone Mac.
This is a fairly intrusive change, but outside of the moving of opal/event to opal/mca/event, the only changes involved (a) changing all calls to opal_event functions to reflect the new framework instead, and (b) ensuring that all opal_event_t objects are properly constructed since they are now true opal_objects.

Note: Shiqing has just returned from vacation and has not yet had a chance to complete the Windows integration. Thus, this commit almost certainly breaks Windows support on the trunk. However, I want this to have a chance to soak for as long as possible before I become less available a week from today (going to be at a class for 5 days, and thus will only be sparingly available) so we can find and fix any problems.

Biggest change is moving the libevent code from opal/event to a new opal/mca/event framework. This was done to make it much easier to update libevent in the future. New versions can be inserted as a new component and tested in parallel with the current version until validated, then we can remove the earlier version if we so choose. This is a statically built framework ala installdirs, so only one component will build at a time. There is no selection logic - the sole compiled component simply loads its function pointers into the opal_event struct.

I have gone thru the code base and converted all the libevent calls I could find. However, I cannot compile nor test every environment. It is therefore quite likely that errors remain in the system. Please keep an eye open for two things:

1. compile-time errors: these will be obvious as calls to the old functions (e.g., opal_evtimer_new) must be replaced by the new framework APIs (e.g., opal_event.evtimer_new)

2. run-time errors: these will likely show up as segfaults due to missing constructors on opal_event_t objects. It appears that it became a typical practice for people to "init" an opal_event_t by simply using memset to zero it out. This will no longer work - you must either OBJ_NEW or OBJ_CONSTRUCT an opal_event_t. I tried to catch these cases, but may have missed some. Believe me, you'll know when you hit it.

There is also the issue of the new libevent "no recursion" behavior. As I described on a recent email, we will have to discuss this and figure out what, if anything, we need to do.

This commit was SVN r23925.
2010-10-24 18:35:54 +00:00
..

0. BUILDING AND INSTALLATION (Briefly)

$ ./configure
$ make
$ make verify   # (optional)
$ sudo make install

1. BUILDING AND INSTALLATION (In Depth)

To build libevent, type

$ ./configure && make

     (If you got libevent from the git repository, you will
      first need to run the included "autogen.sh" script in order to
      generate the configure script.)

Install as root via

# make install

You can run the regression tests by running

$ make verify

Before, reporting any problems, please run the regression tests.

To enable the low-level tracing build the library as:

   CFLAGS=-DUSE_DEBUG ./configure [...]

Standard configure flags should work.  In particular, see:

   --disable-shared          Only build static libraries
   --prefix                  Install all files relative to this directory.


The configure script also supports the following flags:

   --enable-gcc-warnings     Enable extra compiler checking with GCC.
   --disable-malloc-replacement
                             Don't let applications replace our memory
                             management functions
   --disable-openssl         Disable support for OpenSSL encryption.
   --disable-thread-support  Don't support multithreaded environments.

2. USEFUL LINKS:

For the latest released version of Libevent, see the official website at
http://monkey.org/~provos/libevent/ .

There's a pretty good work-in-progress manual up at
   http://www.wangafu.net/~nickm/libevent-book/ .

For the latest development versions of Libevent, access our Git repository
via
   "git clone git://levent.git.sourceforge.net/gitroot/levent/libevent"

You can browse the git repository online at
http://levent.git.sourceforge.net/git/gitweb-index.cgi .

To report bugs, request features, or submit patches to Libevent,
use the Sourceforge trackers at
https://sourceforge.net/tracker/?group_id=50884 .

There's also a libevent-users mailing list for talking about Libevent
use and development: http://archives.seul.org/libevent/users/

3. ACKNOWLEDGMENTS

The following people have helped with suggestions, ideas, code or
fixing bugs:

  Alejo
  Weston Andros Adamson
  William Ahern
  Avi Bab
  Gilad Benjamini
  Stas Bekman
  Joachim Bauch
  Ralph Castain
  Shuo Chen
  Ka-Hing Cheung
  Andrew Danforth
  Christopher Davis
  Mike Davis
  Mihai Draghicioiu
  Shie Erlich
  Alexander von Gernler
  Artur Grabowski
  Sebastian Hahn
  Aaron Hopkins
  Tani Hosokawa
  Claudio Jeker
  Valery Kyholodov
  Marko Kreen
  Scott Lamb
  Christopher Layne
  Adam Langley
  Christopher Layne
  Philip Lewis
  Zhou Li
  David Libenzi
  Moshe Litvin
  Hagne Mahre
  Lubomir Marinov
  Nick Mathewson
  James Mansion
  Nicholas Marriott
  Andrey Matveev
  Caitlin Mercer
  Felix Nawothnig
  Trond Norbye
  Richard Nyberg
  Jon Oberheide
  Phil Oleson
  Dave Pacheco
  Tassilo von Parseval
  Pierre Phaneuf
  Ryan Phillips
  Jon Poland
  Bert JW Regeer
  Hanna Schroeter
  Ralf Schmitt
  Mike Smellie
  Kevin Springborn
  Ferenc Szalai
  Dug Song
  Brodie Thiesfield
  Zack Weinberg
  Taral
  propanbutan
  mmadia

If we have forgotten your name, please contact us.