Brian Barrett wrote:
> On Jul 14, 2007, at 8:26 AM, Dirk Eddelbuettel wrote:
>
>> Please let us (ie Debian's openmpi maintainers) how else we can
>> help. I am
>> ccing the porters lists (for hppa, m68k, mips) too to invite them
>> to help. I
>> hope that doesn't get the spam filters
Welcome! Yes, Jeff and I have been working on the LSF support based on 7.0
features in collab with the folks at Platform.
Some further comments below...
Ralph
On 7/14/07 2:02 PM, "Matthew Moskewicz"
wrote:
> hi everyone,
>
> firstly, i'm new around here, and
the availability of functionality is set by the header files for each
platform, not by configure. So we'd have to play some games to get
at the information, but it should be possible.
Brian
On Jul 14, 2007, at 12:41 PM, George Bosilca wrote:
Brian,
We should be able to use these defines
hi everyone,
firstly, i'm new around here, and somewhat clueless when it comes to the
details of working with an big autoconfiscated project like
open-rte/open-mpi the svn checkout level ...
i've read some of the archives that turned up in searches for terms like
'LSF', and it would seem there
If the OMPI_HAVE_THREAD_SUPPORT is not set the LIFO fall back to a
default version where atomic operations are not required. We can even
remove the dependency on the atomic.h header if the thread support is
not enabled.
Unfortunately, our shared memory device require the atomic operations
On Jul 14, 2007, at 11:51 AM, Gleb Natapov wrote:
On Sat, Jul 14, 2007 at 01:16:42PM -0400, George Bosilca wrote:
Instead of failing at configure time, we might want to disable the
threading features and the shared memory device if we detect that we
don't have support for atomics on a
On Sat, Jul 14, 2007 at 01:16:42PM -0400, George Bosilca wrote:
> Instead of failing at configure time, we might want to disable the
> threading features and the shared memory device if we detect that we
> don't have support for atomics on a specified platform. In a non
> threaded build, the
Instead of failing at configure time, we might want to disable the
threading features and the shared memory device if we detect that we
don't have support for atomics on a specified platform. In a non
threaded build, the shared memory device is the only place where we
need support for
Hi Brian,
On 14 July 2007 at 10:47, Brian Barrett wrote:
| On Jul 14, 2007, at 8:26 AM, Dirk Eddelbuettel wrote:
|
| > Please let us (ie Debian's openmpi maintainers) how else we can
| > help. I am
| > ccing the porters lists (for hppa, m68k, mips) too to invite them
| > to help. I
| >
On Jul 14, 2007, at 10:53 AM, Dirk Eddelbuettel wrote:
Methinks we need to fill in a few blanks here, or make do with non-asm
solutions. I don't know the problem space that well (being a
maintainer
rather than upstream developer) and am looking for guidance.
Either way is an option. There
On Jul 14, 2007, at 8:26 AM, Dirk Eddelbuettel wrote:
Please let us (ie Debian's openmpi maintainers) how else we can
help. I am
ccing the porters lists (for hppa, m68k, mips) too to invite them
to help. I
hope that doesn't get the spam filters going... I may contact the
'arm'
porters
Hi folks,
The 'new' Open MPI packages for Debian that are maintained by a few of us via
a group on alioth.debian.org have now [1] reached the main distribution. This
means they are being built on all supported architecture and logs accumulate at
12 matches
Mail list logo