fceabb2498
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.
100 строки
2.7 KiB
Bash
Исполняемый файл
100 строки
2.7 KiB
Bash
Исполняемый файл
#! /bin/sh
|
|
|
|
# Wrapper for compilers which do not understand `-c -o'.
|
|
|
|
# Copyright 1999, 2000 Free Software Foundation, Inc.
|
|
# Written by Tom Tromey <tromey@cygnus.com>.
|
|
#
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; either version 2, or (at your option)
|
|
# any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program; if not, write to the Free Software
|
|
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
|
|
|
# As a special exception to the GNU General Public License, if you
|
|
# distribute this file as part of a program that contains a
|
|
# configuration script generated by Autoconf, you may include it under
|
|
# the same distribution terms that you use for the rest of that program.
|
|
|
|
# Usage:
|
|
# compile PROGRAM [ARGS]...
|
|
# `-o FOO.o' is removed from the args passed to the actual compile.
|
|
|
|
prog=$1
|
|
shift
|
|
|
|
ofile=
|
|
cfile=
|
|
args=
|
|
while test $# -gt 0; do
|
|
case "$1" in
|
|
-o)
|
|
# configure might choose to run compile as `compile cc -o foo foo.c'.
|
|
# So we do something ugly here.
|
|
ofile=$2
|
|
shift
|
|
case "$ofile" in
|
|
*.o | *.obj)
|
|
;;
|
|
*)
|
|
args="$args -o $ofile"
|
|
ofile=
|
|
;;
|
|
esac
|
|
;;
|
|
*.c)
|
|
cfile=$1
|
|
args="$args $1"
|
|
;;
|
|
*)
|
|
args="$args $1"
|
|
;;
|
|
esac
|
|
shift
|
|
done
|
|
|
|
if test -z "$ofile" || test -z "$cfile"; then
|
|
# If no `-o' option was seen then we might have been invoked from a
|
|
# pattern rule where we don't need one. That is ok -- this is a
|
|
# normal compilation that the losing compiler can handle. If no
|
|
# `.c' file was seen then we are probably linking. That is also
|
|
# ok.
|
|
exec "$prog" $args
|
|
fi
|
|
|
|
# Name of file we expect compiler to create.
|
|
cofile=`echo $cfile | sed -e 's|^.*/||' -e 's/\.c$/.o/'`
|
|
|
|
# Create the lock directory.
|
|
# Note: use `[/.-]' here to ensure that we don't use the same name
|
|
# that we are using for the .o file. Also, base the name on the expected
|
|
# object file name, since that is what matters with a parallel build.
|
|
lockdir=`echo $cofile | sed -e 's|[/.-]|_|g'`.d
|
|
while true; do
|
|
if mkdir $lockdir > /dev/null 2>&1; then
|
|
break
|
|
fi
|
|
sleep 1
|
|
done
|
|
# FIXME: race condition here if user kills between mkdir and trap.
|
|
trap "rmdir $lockdir; exit 1" 1 2 15
|
|
|
|
# Run the compile.
|
|
"$prog" $args
|
|
status=$?
|
|
|
|
if test -f "$cofile"; then
|
|
mv "$cofile" "$ofile"
|
|
fi
|
|
|
|
rmdir $lockdir
|
|
exit $status
|