Hi Cormac,
Thanks so much! It is working now.
Fande,
On Thu, Apr 5, 2018 at 11:21 AM, Garvey, Cormac T
wrote:
> I made some changes to the falcon cluster environment. Please try the
> default git (i.e Without loading a module) and
> see if petsc will install correctly.
>
> Thanks,
> Cormac.
>
I made some changes to the falcon cluster environment. Please try the
default git (i.e Without loading a module) and
see if petsc will install correctly.
Thanks,
Cormac.
On Wed, Apr 4, 2018 at 5:09 PM, Fande Kong wrote:
> The default git gives me:
>
> *Could not execute "['git', 'rev-parse', '-
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 again.
>
> Do you get an
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 as well? Hence we do n
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 git/1.8.5.2-GCC-4.8.3 *
>
> works f
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 cluster because github
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 falcon2
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 from 2009 [sure its
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 o
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:
core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noa
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 2.16.2
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 pla
[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 2.
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 1.8.5.2*
> >
> >
> > This new version does
"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
Can you reproduce the
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 wrote:
> On
On Wed, 7 Mar 2018, Kong, Fande wrote:
> > I meant just the 3 lines - not the whole function.
>
> I knew this. "3 lines" does not work at all.
>
> I forgot the error message.
Then you are likely to use the wrong [git] snapshot - and not the
snapshot listed by self.gitcommit - for that package.
On Wed, Mar 7, 2018 at 2:51 PM, Satish Balay wrote:
> On Wed, 7 Mar 2018, Kong, Fande wrote:
>
> > > If you need to workarround this - you can comment out that test
> (3lines)..
> > >
> > > File "/home/kongf/workhome/projects/petsc-3.7.7/config/
> > > BuildSystem/config/package.py", line 519, i
On Wed, 7 Mar 2018, Kong, Fande wrote:
> > If you need to workarround this - you can comment out that test (3lines)..
> >
> > File "/home/kongf/workhome/projects/petsc-3.7.7/config/
> > BuildSystem/config/package.py", line 519, in updateGitDir
> > gitdir,err,ret =
> > config.base.Configure.
On Wed, Mar 7, 2018 at 1:22 PM, Satish Balay wrote:
> Its strange that you are getting this error in configure - but not command
> linke.
>
> Does the following option make a difference?
>
> --useThreads=0
> or
> --useThreads=1
>
no difference.
>
> If you need to workarround this - you can com
Its strange that you are getting this error in configure - but not command
linke.
Does the following option make a difference?
--useThreads=0
or
--useThreads=1
If you need to workarround this - you can comment out that test (3lines)..
File
"/home/kongf/workhome/projects/petsc-3.7.7/config/B
[kongf@falcon1 git.hypre]$ git rev-parse --git-dir
.git
[kongf@falcon1 git.hypre]$ echo $?
0
[kongf@falcon1 git.hypre]$
[kongf@falcon1 git.hypre]$ git fsck
Checking object directories: 100% (256/256), done.
Checking objects: 100% (22710/22710), done.
[kongf@falcon1 git.hypre]$
But the same err
balay@asterix /home/balay
$ git rev-parse --git-dir
fatal: Not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
balay@asterix /home/balay
$ echo $?
128
balay@asterix /home/balay
$ cd petsc
balay@asterix /home/ba
23 matches
Mail list logo