[petsc-dev] Murky

2010-02-17 Thread Sean Farley
il/petsc-dev/attachments/20100217/de84b753/attachment.html>

[petsc-dev] Murky

2010-02-17 Thread Barry Smith
It is 6 months since the release of snow leopard; what the heck is wrong with the valgrind team beside sheer lazyness? Barry On Feb 17, 2010, at 8:34 PM, Sean Farley wrote: > I finally checked out from valgrind, and configure dies right away > saying it only supports 10.5. > > Matt,

[petsc-dev] Murky

2010-02-17 Thread Sean Farley
hment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/a8b4bc67/attachment.html>

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Lisandro Dalcin
On 17 February 2010 12:00, Matthew Knepley wrote: > I am for a separate mpiuni that get downloaded. I think this makes more > sense with > our other packages concepts, and is more modular. We can reuse so much more > of > configure as well. I still fail to see the pros of having a separate mpiuni

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Lisandro Dalcin
On 17 February 2010 19:14, Jed Brown wrote: > On Wed, 17 Feb 2010 13:32:56 -0300, Lisandro Dalcin > wrote: >> But if they shove a #include "mpi.h" into their source code, things >> will work, as long as they use a true MPI implementation... > > Only as long as PETSc is using their true MPI, it w

[petsc-dev] Murky

2010-02-17 Thread Barry Smith
On Feb 17, 2010, at 6:38 PM, Matthew Knepley wrote: > On Wed, Feb 17, 2010 at 4:29 PM, Barry Smith > wrote: > > Matt, > >I tried it and it reamed me so hard that it will be difficult for > me to ever forgive it. Come on, to have some fuck up that cannot > find hg when it is in the us

[petsc-dev] Murky

2010-02-17 Thread Barry Smith
Matt, I tried it and it reamed me so hard that it will be difficult for me to ever forgive it. Come on, to have some fuck up that cannot find hg when it is in the usual place is so painful I want to cry. Barry Subject:Re: Murky - GUI for mercurial on Mac

[petsc-dev] Murky

2010-02-17 Thread Matthew Knepley
gt;> -- Norbert Wiener >>> >>> >>> >>> >>> -- >>> What most experimenters take for granted before they begin their >>> experiments is infinitely more interesting than any results to which their >>> experiments lead. >>> -- Norbert Wiener >>> >> >> > > > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/83c967c6/attachment.html>

[petsc-dev] Murky

2010-02-17 Thread Matthew Knepley
nitely more interesting than any results to which their >> experiments lead. >> -- Norbert Wiener >> >> >> >> >> -- >> What most experimenters take for granted before they begin their >> experiments is infinitely more interesting than any results to which their >> experiments lead. >> -- Norbert Wiener >> > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/a77d4dff/attachment.html>

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Barry Smith
We want both the transparency and simplicity to the user PLUS a common way of handling things in PETSc to reduce the learning curve of PETSc developers and PETSc maintenance. Each "special case" in PETSc is a flaw in our design, and an admission we made a mistake or didn't really k

[petsc-dev] Murky

2010-02-17 Thread Matthew Knepley
ich their >> experiments lead. >> -- Norbert Wiener >> > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/0cad4a04/attachment.html>

[petsc-dev] Murky

2010-02-17 Thread Matthew Knepley
ments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/a222e77c/attachment.html>

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Lisandro Dalcin
On 17 February 2010 14:31, Barry Smith wrote: > > ?Hmm, with code like > > #ifdef SYSDARWIN > #include "string.h" > #endif > > I think I'll pass on this software. > Yep, after looking at the actual code (for example, things like "if (root!=0) {printf("error"); abort();}" ), I have to agree with y

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Jed Brown
On Wed, 17 Feb 2010 13:32:56 -0300, Lisandro Dalcin wrote: > But if they shove a #include "mpi.h" into their source code, things > will work, as long as they use a true MPI implementation... Only as long as PETSc is using their true MPI, it will not work at all if PETSc was built with mpiuni. (

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Matthew Knepley
ke for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/bd378206/attachment.html>

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Lisandro Dalcin
On 17 February 2010 13:38, Matthew Knepley wrote: > > I do not think this handles the situation for libraries. I write a library. > It is > supposed to work with lots of stuff, including PETSc. I put in mpi.h, which > is completely reasonable. Then the user of the library wants to use mpiuni. > W

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Lisandro Dalcin
On 17 February 2010 13:06, Barry Smith wrote: > > On Feb 17, 2010, at 9:05 AM, Lisandro Dalcin wrote: > >> On 17 February 2010 11:45, Barry Smith wrote: >>> >>> 1) Make mpiuni truly a download package mimicing other ones exactly. >>> 2) Swallow mpiuni more completely into PETSc, no separate libmp

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Lisandro Dalcin
On 17 February 2010 11:45, Barry Smith wrote: > > 1) Make mpiuni truly a download package mimicing other ones exactly. > 2) Swallow mpiuni more completely into PETSc, no separate libmpiuni, put the > includes/mods in a location they are found automatically without the extra > -I > 3) Have a ha

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Barry Smith
Hmm, with code like #ifdef SYSDARWIN #include "string.h" #endif I think I'll pass on this software. Barry On Feb 17, 2010, at 11:12 AM, Lisandro Dalcin wrote: > On 17 February 2010 13:38, Matthew Knepley wrote: >> >> I do not think this handles the situation for libraries. I write a

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Barry Smith
On Feb 17, 2010, at 10:32 AM, Lisandro Dalcin wrote: > On 17 February 2010 13:06, Barry Smith wrote: >> >> On Feb 17, 2010, at 9:05 AM, Lisandro Dalcin wrote: >> >>> On 17 February 2010 11:45, Barry Smith wrote: 1) Make mpiuni truly a download package mimicing other ones exactl

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Barry Smith
On Feb 17, 2010, at 9:05 AM, Lisandro Dalcin wrote: > On 17 February 2010 11:45, Barry Smith wrote: >> >> 1) Make mpiuni truly a download package mimicing other ones exactly. >> 2) Swallow mpiuni more completely into PETSc, no separate >> libmpiuni, put the >> includes/mods in a location they

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Barry Smith
On Feb 16, 2010, at 10:59 PM, Satish Balay wrote: > On Tue, 16 Feb 2010, Satish Balay wrote: > >> On Tue, 16 Feb 2010, Barry Smith wrote: >> >>> >>> Satish, >>> >>> Why not get rid of libmpiuni completely? Just stick the code into >>> libpetscsys.a for multiple libraries and libpetsc.a for one l

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Matthew Knepley
; --- > Centro Internacional de M?todos Computacionales en Ingenier?a (CIMEC) > Instituto de Desarrollo Tecnol?gico para la Industria Qu?mica (INTEC) > Consejo Nacional de Investigaciones Cient?ficas y T?cnicas (CONICET) > PTLC - G?emes 3450, (3000) Santa Fe, Argentina > Tel/Fax: +54-(0)342-451.1594 > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/3ae7cb97/attachment.html>

[petsc-dev] forget about libmpiuni completely

2010-02-17 Thread Matthew Knepley
simplify its code maintainance. >>> >>> Note: I would have liked to have libmpiuni.a as separate library even >>> with --with-single-library=1 - but due to the way >>> --with-single-library=1 is done - its not possible - so I gave up on >>> that. >>> >> > If there is no libmpiuni with a single library then there should be none > with several libraries, otherwise it is confusingly inconsistent. > > Barry > > >>> Satish >>> >>> >> > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100217/cb53f8b3/attachment.html>