lles Gouaillardet wrote:
>
> Karol,
>
>
> is there any place i can download glibc 2.24 for tumbleweed ?
>
>
> i'd like to have a look at what is going wrong with openmpi 1.10
>
>
> Cheers,
>
>
> Gilles
>
> On 8/25/2016 10:24 AM, Karol Mroz wrot
e one provided by
> Open MPI ?
>
>
> fwiw, Open MPI 1.10.4 and 2.0.1 should be released in a near future.
>
>
> Cheers,
>
>
> Gilles
>
> On 8/25/2016 10:24 AM, Karol Mroz wrote:
>
> Greetings!
>
> I would like to upgrade our (openSUSE Tumbleweed) version of Open
Greetings!
I would like to upgrade our (openSUSE Tumbleweed) version of Open MPI from
1.10.3 to the shiny new 2.0.0 :) This is motivated by a number of factors,
including an upgrade to glibc2.24 which breaks our current build of Open
MPI. I thought it a great time to push out a new version :D
The
t: Re: [OMPI devel] Build failure on FreeBSD 7
This may depend on how you ran the app on FreeBSD -- did you run on
the localhost only?
We have/had a problem when running locally with regards to kevent --
I'm not 100% sure if we've fixed it yet. Let me check...
On Apr 5, 2008, at 1:53
After digging a little deeper, it turns out that the kevent() call in
opal/event/kquene.c:
if (kevent(kq,
kqueueop->changes, 1, kqueueop->events, NEVENT, NULL) != 1 ||
(int)kqueueop->events[0].ident != master ||
kqueueop->events[0].flags != EV_ERROR) {
see
Hello everyone... it's been some time since I posted here. I pulled the
latest svn revision (18079) and had some trouble building Open MPI on a
FreeBSD 7 machine (i386).
Make failed when compiling opal/event/kqueue.c. It appears that freebsd
needs sys/types.h, sys/ioctl.h, termios.h and libuti
___
>>>>>> devel mailing list
>>>>>> de...@open-mpi.org
>>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>>>>
>>>>> --
>>>>> Jeff Squyres
>>>>> Cisco Systems
>>>>> _____
Hi...
Karol Mroz wrote:
> Removal of .ompi_ignore should not create build problems for anyone who
> is running without some form of SCTP support. To test this claim, we
> built Open MPI with .ompi_ignore removed and no SCTP support on both an
> ubuntu linux and an OSX machine.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Jeff... thanks for getting back to me.
Jeff Squyres wrote:
> On Nov 29, 2007, at 12:13 PM, Karol Mroz wrote:
>
>>> One solution might be to remove the .ompi_ignore but to only enable
>>> the SCTP BTL when an explicit --wi
ntly, will not break the build of the
overall system.
My question now, is it necessary for us to alter the above
behavior (as initially mentioned by Jeff), or is having the SCTP BTL
build iff SCTP is found sufficient?
Thanks in advance for any advice on this matter.
- --
Karol Mroz
km...@cs.ub
popd > /dev/null 2>&1
unset indent
- ---
Thanks.
- --
Karol Mroz
km...@cs.ubc.ca
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHK3LFuoug78g/Mz8RAvIDAJ9+XiEdY24
rol,
>
> * Karol Mroz wrote on Wed, Sep 19, 2007 at 07:23:50PM CEST:
>> When running the autogen.sh script as non-root, I see the following error:
> [...]
>> autom4te-2.61: cannot open configure: Permission denied
> [...]
>> After some searching, it would appe
ll only happen when the developer debugging code is
> enabled, which is the default when building from a subversion checkout.
>
> Thanks again for your reports,
>
> Tim
>
> Karol Mroz wrote:
>> Hi. I have been trying to build the latest ompi-trunk (as of yesterday)
&g
source or build scripts were being generated incorrectly on FreeBSD.
However, this yielded the same errors with ompi-trunk as mentioned above.
Any ideas?
--
Karol Mroz
km...@cs.ubc.ca
7, at 4:56 PM, Karol Mroz wrote:
Good morning everyone. I had a question about obtaining the message tag
from the iovec array in mca_btl_sctp_frag_t* frag from within the
mca_btl_tcp_frag_send() function. If I understand correctly, the first X
bytes in the first iovec entry contain mess
L agnostic.
Thanks,
george.
On Jul 2, 2007, at 4:56 PM, Karol Mroz wrote:
Good morning everyone. I had a question about obtaining the message tag
from the iovec array in mca_btl_sctp_frag_t* frag from within the
mca_btl_tcp_frag_send() function. If I understand correctly, the first X
bytes in
x27;m overlooking... any help would be appreciated.
Thanks,
Karol
--
Karol Mroz
km...@cs.ubc.ca
a portion if it is over a certain size. The new series of iovecs are
then individually passed to writev(). There is probably a more elegant
solution and one in which the original frag pointer has knowledge of
what is going on.
--
Karol Mroz
km...@cs.ubc.ca
er book keeping in
the event of an interrupted send create problems?
Any ideas on this matter would be greatly appreciated.
--
Karol Mroz
km...@cs.ubc.ca
19 matches
Mail list logo
