Updated:
If switch to a different version of git. The configuration is going to
work.
This one works:
* petsc]$ git --version git version 1.8.5.2*
This new version does not work:
petsc]$ git --version
git version 2.16.2
Fande.
On Wed, Mar 7, 2018 at 2:56 PM, Satish Balay
We needed to rebuilt git on the INL falcon cluster because github server
changed such that it no longer accepted TLSv1.
The default git on the falcon cluster /usr/bin/git is just a wrapper
script, so users would not need to load any modules to
use git.
When you load load git on falcon1 or
moose]$ uname -a
Linux falcon1 3.0.101-108.13-default #1 SMP Wed Oct 11 12:30:40 UTC 2017
(294ccfe) x86_64 x86_64 x86_64 GNU/Linux
moose]$ lsb_release -a
LSB Version:
Thanks, Cormac,
*module load git/1.8.5.2-GCC-4.8.3 *
works for me.
Did not try "module load git/2.16.2-GCCcore-5.4.0" yet.
I will try, and get it back here.
Fande
On Wed, Apr 4, 2018 at 4:39 PM, Garvey, Cormac T
wrote:
>
> We needed to rebuilt git on the INL falcon
Ok - I don't think I have access to this OS.
And I see its from 2009 [sure its enterprise os - with regular backport updates]
But its wierd that you have such a new version of git at /usr/bin/git
>From what we know so far - the problem appears to be some bad
interaction of python-2.6 with this
On Wed, Apr 4, 2018 at 3:55 PM, Jed Brown wrote:
> "Kong, Fande" writes:
>
> > Updated:
> >
> > If switch to a different version of git. The configuration is going to
> > work.
> >
> >
> > This one works:
> >
> >
> > * petsc]$ git --version git version
The default git gives me:
*Could not execute "['git', 'rev-parse', '--git-dir']"*
when I am configuring PETSc.
The manually loaded *gits* work just fine.
Fande,
On Wed, Apr 4, 2018 at 5:04 PM, Garvey, Cormac T
wrote:
> I though it was fixed, yes I will look into it
"Kong, Fande" writes:
> Updated:
>
> If switch to a different version of git. The configuration is going to
> work.
>
>
> This one works:
>
>
> * petsc]$ git --version git version 1.8.5.2*
>
>
> This new version does not work:
>
> petsc]$ git --version
> git version 2.16.2
module load git/2.16.2-GCCcore-5.4.0" also works.
Could you somehow make the default git work as well? Hence we do not need
to have this extra "module load for git"
Fande,
On Wed, Apr 4, 2018 at 4:43 PM, Kong, Fande wrote:
> Thanks, Cormac,
>
> *module load
I though it was fixed, yes I will look into it again.
Do you get an error just doing a git clone on falcon1 and falcon2?
On Wed, Apr 4, 2018 at 4:48 PM, Kong, Fande wrote:
> module load git/2.16.2-GCCcore-5.4.0" also works.
>
> Could you somehow make the default git work
On Wed, 4 Apr 2018, Satish Balay wrote:
> was your '2.16.2' version installed from source?
>>>
Checking for program /usr/bin/git...found
Defined make macro "GIT" to "git"
Executing: git --version
stdout: git version 2.16.2
I gues its the OS default package
>
Machine
Hi Cormac,
Do you know anything on "git"? How did you guys build git on the falcon1?
The default git on Falcon1 does not work with petsc any more.
Fande,
On Wed, Apr 4, 2018 at 4:20 PM, Satish Balay wrote:
> Ok - I don't think I have access to this OS.
>
> And I see its
[balay@fedora ~]$ cat /etc/fedora-release
Fedora release 27 (Twenty Seven)
[balay@fedora ~]$ git --version
git version 2.14.3
[balay@fedora ~]$
balay@asterix /home/balay
$ cat /etc/fedora-release
Fedora release 28 (Twenty Eight)
balay@asterix /home/balay
$ git --version
git version
On Wed, 4 Apr 2018, Satish Balay wrote:
> On Wed, 4 Apr 2018, Satish Balay wrote:
>
> > was your '2.16.2' version installed from source?
>
> >>>
> Checking for program /usr/bin/git...found
> Defined make macro "GIT" to "git"
> Executing: git --version
> stdout: git version
On Thu, Mar 29, 2018 at 1:48 AM, TAY wee-beng wrote:
>
> On 28/3/2018 5:45 PM, Matthew Knepley wrote:
>
> On Tue, Mar 27, 2018 at 10:17 PM, TAY wee-beng wrote:
>
>> Hi Dave,
>>
>> I looked at the output using log_view and re-compile. However, although I
>>
Hi Yann,
On Tue, Apr 03, 2018 at 05:29:39PM +0200, Yann Jobic wrote:
> Hi,
>
> Thanks for the fast answer ! And sorry for my late one...
> As a test, i'm using ex2.c in test/forest directory.
>
> I'm using 2 git depot (master), one from this week end, and one of today. I
> see some different
Hi Isaac,
It's working !!
Many thanks !
Regards,
Yann
Le 04/04/2018 à 15:18, Tobin Isaac a écrit :
Hi Yann,
On Tue, Apr 03, 2018 at 05:29:39PM +0200, Yann Jobic wrote:
Hi,
Thanks for the fast answer ! And sorry for my late one...
As a test, i'm using ex2.c in test/forest directory.
I'm
On Tue, Apr 3, 2018 at 9:24 PM, Xiangdong wrote:
> Hello everyone,
>
> The latest Hypre has GPU capability. Can I use hypre GPU feature through
> PETSc? If it is possible, what configuration changes should I make in PETSc?
>
It should work. I don't if anyone has used it yet.
Our config/BuildSystem/config/packages/hypre.py does not yet have code to
communicate GPU information for building hypre. One would need to go through
the hypre install documentation to determine the hypre configure flags for
enabling the GPU and add support to hypre.py for passing these
Hi,
I emailed as shown below a while ago but I have yet to get a response.
Can someone help?
Thank you very much.
Yours sincerely,
TAY Wee-Beng (Zheng Weiming) 郑伟明
Personal research webpage: http://tayweebeng.wixsite.com/website
Youtube
20 matches
Mail list logo