George Bosilca e58b611512 dirname have a different behavior depending on the operating system. ...

opal_dirname have the same behavior all the time. It does not modify
the original string and it returns a freshly allocated string.

This commit was SVN r11443.

2006-08-27 05:09:40 +00:00

..

asm

* IA64 can have a weaker consistency model for memory than x86, so we

2006-06-17 05:01:54 +00:00

class

One typo and one UNIX conversion of EOL.

2006-08-25 23:22:35 +00:00

etc

Update comments to clarify how this file is used.

2006-06-05 13:59:43 +00:00

event

* don't need to extern these here -- already done earlier in header file.

2006-08-24 13:48:17 +00:00

include

Don't keep a special case for Windows as it's wrong. The problem is that

2006-08-25 23:16:49 +00:00

mca

On Windows use the high performance timers ... differently or lose

2006-08-27 04:56:20 +00:00

memoryhooks

Remove all references to the removed files.

2006-08-23 02:18:24 +00:00

runtime

* fix the comment, too

2006-08-24 14:06:01 +00:00

threads

* Default the value of opal_uses_threads (which is used by the macro

2006-08-24 13:57:26 +00:00

tools

Remove the latest set of warnings (catched by gcc 4). Now everything

2006-08-23 00:48:05 +00:00

util

dirname have a different behavior depending on the operating system.

2006-08-27 05:09:40 +00:00

win32

Did it say miliseconds ?

2006-08-27 04:53:52 +00:00

Makefile.am

* forgot to add new directories into DIST_SUBDIRS as well as SUBDIRS, so

2006-02-12 07:06:38 +00:00

win_makefile

Move all win32 related files in opal, and modify all the Makefiles.am to

2005-12-08 06:17:15 +00:00