B1;2601;0cOn Wed, 3 Nov 2010, Carl Ponder wrote:
> ps -- I'm working through a problem with the PetscTruth still being
> used in the SAMRAI code.
> I still see a few instances in the PETSc code as well; is this
> something that is supposed to go away?
Yes - its all supporsed to go away.
balay
On Wed, 3 Nov 2010, Bobby Philip wrote:
> As far as I can tell SAMRAI uses petsc assuming the C style calls
> for petsc.
Yeah - the issue comes up when building PETSc with a c compiler - and
then compiling user code [in this case SAMRAI] that includes petsc.h
with c++ compiler.
> In cases where
Guys:
As far as I can tell SAMRAI uses petsc assuming the C style calls for petsc. In
cases where
I have enabled C++ in PETSc it has broken SAMRAI.
Bobby
On Nov 3, 2010, at 7:50 PM, Satish Balay wrote:
> I think I understand the issue. I'm pushing something that should fix it.
>
> [so here -
-
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/061cecaa/attachment.html>
hg pull; hg update; cd src/sys/viewer/impls/hdf5; make
Barry
Someone's incomplete and untested cut and paste snuck into the repository
On Nov 3, 2010, at 8:55 PM, Carl Ponder wrote:
>
> Satish, Jed -- I'm not sure the message got through -- here's the info
> without the log files:
>
>
stribution
is prohibited. If you are not the intended recipient, please contact the
sender by
reply email and destroy all copies of the original message.
---
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/d17237c1/attachment.html>
On Nov 3, 2010, at 7:50 PM, Jed Brown wrote:
> On Wed, Nov 3, 2010 at 19:48, Barry Smith wrote:
> I would say it was spurious, but users building PETSc won't know it is
> spurious and I like clean compiles with no warnings (even if the warnings are
> wrong).
>
> Okay, then PETSc needs to avo
r a struct and
member. Is this thread really the only one?
Jed
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/cdce485b/attachment.html>
On Nov 3, 2010, at 7:44 PM, Jed Brown wrote:
> On Wed, Nov 3, 2010 at 12:50, Barry Smith wrote:
> Because of the || *r2 may never get set, but it gets used later in the
> routine. Maybe compilers shouldn't give the warning but some did.
>
> But the uninitialized value can't be used if PetscMal
--- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/c48c6eb1/attachment.html>
I think I understand the issue. I'm pushing something that should fix it.
[so here - you have to do 'hg pull -u' to get this fix and rerun configure]
Jed,
The issue is: PETSc is built without a c++ compiler, but SAMRAI - is
using it with c++ - hence the error [with missing
PETSC_FUNCTION_NAME_CX
On Wed, 3 Nov 2010, Carl Ponder wrote:
> *On 11/03/2010 06:31 PM, Satish Balay wrote:*
>
> > Perhaps we are misinterpriting the errors from the snippets sent
> > earlier. Please send the complete logs [configure.log and
> > make.log] to petsc-maint so that we can diagnose the issue pr
y
reply email and destroy all copies of the original message.
---
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/2f587af0/attachment.html>
permail/petsc-dev/attachments/20101103/0edaeb55/attachment.html>
On Wed, 3 Nov 2010, Carl Ponder wrote:
> *On 11/03/2010 06:07 PM, Satish Balay wrote:*
> >
> > You have some contradictory statements here:
> >
> > " Note that while I pulled BuildSystem,"
> > " although I'm skipping the steps"
> > " hg pull -u"
> >
> > How did you pull Buil
s
> of the original message.
> --
>
>
--
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/20101103/8359acf0/attachment.html>
ited. If you are not the intended recipient, please contact the
sender by
reply email and destroy all copies of the original message.
---
-- next part ------
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/e4e331f2/attachment.html>
art --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/f4f56153/attachment.html>
You have some contradictory statements here:
" Note that while I pulled BuildSystem,"
" although I'm skipping the steps"
" hg pull -u"
How did you pull BuildSystem - if not with 'hg pull -u'? [same with petsc-dev]
[I'm assuming you've done 'hg clone' a few days ago - not today]
Just to be su
s of the original message.
---
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/5ba7d803/attachment.html>
t the intended recipient, please contact the
> > sender by
> > reply email and destroy all copies of the original message.
> >
> ---
> >
>
>
--
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/20101103/abedaa88/attachment.html>
Perhaps you pulled petsc-dev - but not BuildSystem - so they are out-of-sync?
Satish
On Wed, 3 Nov 2010, Carl Ponder wrote:
>
> Satash -- the filepetsc-dev/include/petscsys.h contains a statement
>
>25 #if defined(__cplusplus)
>*26 # define PETSC_FUNCTION_NAME PETSC_FUNCTION_NAME_
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/ce693af2/attachment.html>
; >> Matt
> >>
> >>
> >
>
>
------ next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/1f458232/attachment.html>
On Wed, 3 Nov 2010, Matthew Knepley wrote:
> Since you use our version control system, you will never have to worry
> about something breaking. If something does not work after a pull, just
>
> a) rollback to the previous revision, 'hg update -r '
Or if you don't remember the previous 'working
re not the intended recipient, please contact the
> > sender by
> > reply email and destroy all copies of the original message.
> >
> ---
> >
>
>
--
What most experimenters tak
Victor,
I have a new image 'lucid-amd64-cuda32-ib-tmp1' - you can give it a try.
Satish
On Wed, 3 Nov 2010, Victor Minden wrote:
> The cuda version is currently checked in setcompilers.py at the same time as
> it looks for nvcc, though maybe this is a bad place for it. Regardless, I
> changed
On Wed, 3 Nov 2010, Carl Ponder wrote:
> *On 11/03/2010 01:33 PM, Satish Balay wrote:*
>
> > for http there is no '$USER:$PASSWORD@' in the URL [I guess its just
> > ignored - so it works..]
> > I pushed a fix now.. You can pull and retry [after 'hg revert configure'
> > - to remove your
l copies of the original message.
---
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/e1037906/attachment.html>
On Wed, 3 Nov 2010, Satish Balay wrote:
> >./configure --with-cc=gcc --with-fc=mpif90
> >--download-f-blas-lapack=1 --download-mpich=1 --download-hdf5=1
BTW: the above is inconsistant.
If you already have mpif90 - then you should have a corresponding
mpicc to use [ so use '--with-cc=mpic
On Wed, 3 Nov 2010, Carl Ponder wrote:
>
> I just copied thepetsc-dev subtree using the commands
>
>hg clone http://$USER:$PASSWORD at petsc.cs.iit.edu/petsc/petsc-dev
for http there is no '$USER:$PASSWORD@' in the URL [I guess its just ignored -
so it works..]
>cd petsc-dev/config
osure or
distribution
is prohibited. If you are not the intended recipient, please contact the
sender by
reply email and destroy all copies of the original message.
---
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/232edc39/attachment.html>
On Nov 3, 2010, at 11:39 AM, Jed Brown wrote:
> [moving to petsc-dev]
>
> On Wed, Nov 3, 2010 at 10:54, Barry Smith wrote:
> Right, this is very bad. We set the r2 and r3 up front so the compiler won't
> complain about possible not set values?
>
> I don't know, you wrote that code. I strippe
On Nov 3, 2010, at 12:03 PM, Satish Balay wrote:
> Will check the machine. Perhaps cuda.py needs version check - similar
> to cusp.py?
>
Yes, it should have one.
Barry
> satish
>
> On Wed, 3 Nov 2010, Matthew Knepley wrote:
>
>> Thanks,
>>
>> Matt
>>
>>
>
Will check the machine. Perhaps cuda.py needs version check - similar
to cusp.py?
satish
On Wed, 3 Nov 2010, Matthew Knepley wrote:
> Thanks,
>
>Matt
>
>
ront.
Jed
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/597bff50/attachment.html>
36 matches
Mail list logo
