On Dec 10, 2008, at 2:01 PM, Rainer Keller wrote:
Ralph,
we delayed the COB for this to 9.12., announced yesterday to prepare
to commit
today.
We updated to get new buglets that were fixed, tested twice on Win
(shared&static) and Linux to see that nothing breaks
Sounds great!
Now we are
Ralph,
we delayed the COB for this to 9.12., announced yesterday to prepare to commit
today.
We updated to get new buglets that were fixed, tested twice on Win
(shared&static) and Linux to see that nothing breaks
Now we are ready to commit and just as well get a r20106 which touches quite a
cod
Shiqing,
Don't waste your time. While the idea behind cccl is nice, the
overhead is unbelievably expensive. As a comparison it took 2 hours to
compile Open MPI on Windows using cccl and makefile, while it takes
less than 4 minutes to compile exactly the same set of functionalities
using t
Hi Ralf,
Sorry for replying late.
what keeps you from using the autotools-based build system
with MSVC? All you should need is a wrapper like cccl.
I didn't know this 'cccl' before, but I did give a try last weekend with
Cygwin.
Unfortunately, I couldn't make it work for Open MPI (late
Hi Rainer
Historically, our rules have prohibited the introduction of such
features into a sub-release like 1.3.1. Perhaps that policy needs
review?
We've been pretty strict about it in the past, though...with some good
reasons, I admit.
Ralph
On Nov 20, 2008, at 4:56 PM, Rainer Kelle
Hi Ralph,
On Donnerstag, 20. November 2008, Ralph Castain wrote:
> 1. since nearly everyone is at SC08, and since next week is a holiday,
> the timing of this merge is poor. I would really urge that you delay
> it until at least Dec 5 so people actually know about it - and have
> time to even think
I'm probably going to come across as ignorant, and I'm
obviously biased on this matter, but:
* Tim Mattox wrote on Thu, Nov 20, 2008 at 02:53:13PM CET:
>
> Although I don't use windows myself, I appreciate your
> and others' efforts to expand the number of platforms
> we can run on. Great work!
Hi Ralph,
1. since nearly everyone is at SC08, and since next week is a holiday,
the timing of this merge is poor. I would really urge that you delay
it until at least Dec 5 so people actually know about it - and have
time to even think about it
No problem, we can delay it. Dec 9th is the last
Hi Tim,
Yes, you're right. Most of those changes are made based on #ifdef
__WINDOWS__, that would make troubles for CMRs.
Here I provide some more information :
These files are harmless, because no other platform will use them (no need to
go into 1.3).
HmmmI was just typing this up when Tim's note hit. I also have two
concerns that somewhat echo his:
1. since nearly everyone is at SC08, and since next week is a holiday,
the timing of this merge is poor. I would really urge that you delay
it until at least Dec 5 so people actually know
I have two concerns. First is that we really need to focus on
getting 1.3 stable and released. My second concern with
this is how will it effect merging of bugfixes for 1.3 from the
trunk once we release 1.3. Will the following modified files
cause merge conflicts for CMRs? How big is this diff
11 matches
Mail list logo
