"Balay, Satish via petsc-dev" writes:
> Hm for CXXFLAGS - I think you have to do:
>
> self.pushLanguage('Cxx')
> CXXFLAGS = self.getCompilerFlags()
> self.popLanguage()
These days, it's better to write this using the context manager:
with self.Language('Cxx'):
CXXFLAGS = self.getCompilerF
On Mon, 25 Mar 2019, Mills, Richard Tran via petsc-dev wrote:
> Folks,
>
> I've spent a while looking at the BuildSystem code, and I think this is going
> to take me more time than I have available right now to figure it out on my
> own. Someone more familiar with BuildSystem needs to give me s
On Mon, 25 Mar 2019, Mills, Richard Tran via petsc-dev wrote:
> Folks,
>
> I've spent a while looking at the BuildSystem code, and I think this is going
> to take me more time than I have available right now to figure it out on my
> own. Someone more familiar with BuildSystem needs to give me s
Folks,
I've spent a while looking at the BuildSystem code, and I think this is going
to take me more time than I have available right now to figure it out on my
own. Someone more familiar with BuildSystem needs to give me some hints --
soon, if possible, as I really think that building with non
On 3/22/19 3:28 PM, Mills, Richard Tran wrote:
On 3/22/19 12:13 PM, Balay, Satish wrote:
Is there currently an existing check like this somewhere? Or will things just
fail when running 'make' right now?
Most likely no. Its probably best to attempt the error case - and
figure-out how to add a
On 3/22/19 12:13 PM, Balay, Satish wrote:
Is there currently an existing check like this somewhere? Or will things just
fail when running 'make' right now?
Most likely no. Its probably best to attempt the error case - and
figure-out how to add a check.
I gave things a try and verified that t
> Is there currently an existing check like this somewhere? Or will things just
> fail when running 'make' right now?
>
Most likely no. Its probably best to attempt the error case - and
figure-out how to add a check.
Satish
On Fri, 22 Mar 2019, Mills, Richard Tran via petsc-dev wrote:
> On 3/1
On 3/18/19 7:29 PM, Balay, Satish wrote:
On Tue, 19 Mar 2019, Mills, Richard Tran via petsc-dev wrote:
Colleagues,
It took me a while to get PETSc to build at all with anything on Summit other
than the GNU compilers, but, once this was accomplished, editing out the
isGNU() test and then pass
On Tue, 19 Mar 2019, Mills, Richard Tran via petsc-dev wrote:
> Colleagues,
>
> It took me a while to get PETSc to build at all with anything on Summit other
> than the GNU compilers, but, once this was accomplished, editing out the
> isGNU() test and then passing something like
>
> '--wit
Colleagues,
It took me a while to get PETSc to build at all with anything on Summit other
than the GNU compilers, but, once this was accomplished, editing out the
isGNU() test and then passing something like
'--with-cuda=1',
'--with-cudac=nvcc -ccbin pgc++',
to configure works fine. So
Hi Richard,
the check for the GNU compilers is mostly a historic relic. We haven't
done any systematic tests with other compilers, so that test has just
remained in place.
It would certainly be good if you could update the check to also work
well with the default environment on Summit.
Tha
On 3/12/19 8:49 PM, Balay, Satish wrote:
1. You might want to check 'Feature-request: Must use GNU compilers
with CUDA' thread on petsc-maint.
Yes, I see this thread now. Thanks.
2. what does nvcc use internally on summit?
It defaults to the GCC suite but it is supposed to also support the
Jed, yes, I'm on petsc-maint and I see this thread now. Thanks; I'll take a
look. (I've had a crazy day and have been more behind than usual on email.)
--Richard
On 3/12/19 8:48 PM, Jed Brown wrote:
Richard, are you not on petsc-maint? There was a thread about this today.
PGI "community editi
1. You might want to check 'Feature-request: Must use GNU compilers
with CUDA' thread on petsc-maint.
2. what does nvcc use internally on summit?
3. On linux - nvcc defaults to using g++ internally (as far as I know)
- so we added that check. But you might want to remove that check - if
things wo
Richard, are you not on petsc-maint? There was a thread about this today.
PGI "community edition" is free now. We could add it to our test suite.
https://www.pgroup.com/products/community.htm
"Smith, Barry F. via petsc-dev" writes:
> Richard,
>
> You need to remove the isGNU() test a
Richard,
You need to remove the isGNU() test and then experiment with getting the
Nvidia tools to use the compiler you want it to use.
No one has made a serious effort to use any other compilers but Gnu (at
least not publicly).
Barry
> On Mar 12, 2019, at 10:40 PM, Mills, Ri
Fellow PETSc developers,
If I try to configure PETSc with CUDA support on the ORNL Summit system using
non-GNU compilers, I run into an error due to the following code in
packages/cuda.py:
def configureTypes(self):
import config.setCompilers
if not config.setCompilers.Configure.isGNU(
17 matches
Mail list logo
