Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-05 Thread Kong, Fande
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.
>
> On Wed, Apr 4, 2018 at 5:09 PM, Fande Kong  wrote:
>
>> 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 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 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 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 <
> cormac.gar...@inl.gov> wrote:
>
>>
>> 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 does it still fail?
>>
>> module load git/2.16.2-GCCcore-5.4.0
>>
>> Thanks,
>> Cormac.
>>
>>
>>
>> On Wed, Apr 4, 2018 at 4:28 PM, Kong, Fande 
>> wrote:
>>
>>> 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 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 old OS [i.e old glibc etc..] -
 and
 this new git version [binary built locally or on a different OS and
 installed locally ?].

 Satish

 On Wed, 4 Apr 2018, Kong, Fande wrote:

 >  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:deskto
 p-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics
 -3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4
 .0-noarch
 > Distributor ID:SUSE LINUX
 > Description:SUSE Linux Enterprise Server 11 (x86_64)
 > Release:11
 > Codename:n/a
 >
 >
 >
 > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay 
 wrote:
 >
 > > 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
 > > > 
 > > >
 > > > I gues its the OS default package
 > > >
 > > > >
 > > > Machine platform:
 > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed
 Oct 11
 > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
 > > > Python version:
 > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
 > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
 > > > 
 > > >
 > > > What OS/version is on this machine? I can try reproducing in
 a VM
 > >
 > > It is strange that the 

Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-05 Thread Garvey, Cormac T
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', '--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 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 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 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
> 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 does it still fail?
>
> module load git/2.16.2-GCCcore-5.4.0
>
> Thanks,
> Cormac.
>
>
>
> On Wed, Apr 4, 2018 at 4:28 PM, Kong, Fande 
> wrote:
>
>> 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 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 old OS [i.e old glibc etc..] -
>>> and
>>> this new git version [binary built locally or on a different OS and
>>> installed locally ?].
>>>
>>> Satish
>>>
>>> On Wed, 4 Apr 2018, Kong, Fande wrote:
>>>
>>> >  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:deskto
>>> p-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics
>>> -3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4
>>> .0-noarch
>>> > Distributor ID:SUSE LINUX
>>> > Description:SUSE Linux Enterprise Server 11 (x86_64)
>>> > Release:11
>>> > Codename:n/a
>>> >
>>> >
>>> >
>>> > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay 
>>> wrote:
>>> >
>>> > > 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
>>> > > > 
>>> > > >
>>> > > > I gues its the OS default package
>>> > > >
>>> > > > >
>>> > > > Machine platform:
>>> > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct
>>> 11
>>> > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
>>> > > > Python version:
>>> > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
>>> > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
>>> > > > 
>>> > > >
>>> > > > What OS/version is on this machine? I can try reproducing in a
>>> VM
>>> > >
>>> > > It is strange that the kernel is old [3.0 - perhaps LTS OS] ,
>>> python is
>>> > > old [2.6] - but git is new? [2.16?]
>>> > >
>>> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__
>>> > > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
>>> > > 

Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Fande Kong
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 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 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 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
 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 does it still fail?

 module load git/2.16.2-GCCcore-5.4.0

 Thanks,
 Cormac.



 On Wed, Apr 4, 2018 at 4:28 PM, Kong, Fande  wrote:

> 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 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 old OS [i.e old glibc etc..] - and
>> this new git version [binary built locally or on a different OS and
>> installed locally ?].
>>
>> Satish
>>
>> On Wed, 4 Apr 2018, Kong, Fande wrote:
>>
>> >  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:deskto
>> p-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics
>> -3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
>> > Distributor ID:SUSE LINUX
>> > Description:SUSE Linux Enterprise Server 11 (x86_64)
>> > Release:11
>> > Codename:n/a
>> >
>> >
>> >
>> > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay 
>> wrote:
>> >
>> > > 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
>> > > > 
>> > > >
>> > > > I gues its the OS default package
>> > > >
>> > > > >
>> > > > Machine platform:
>> > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct
>> 11
>> > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
>> > > > Python version:
>> > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
>> > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
>> > > > 
>> > > >
>> > > > What OS/version is on this machine? I can try reproducing in a
>> VM
>> > >
>> > > It is strange that the kernel is old [3.0 - perhaps LTS OS] ,
>> python is
>> > > old [2.6] - but git is new? [2.16?]
>> > >
>> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__
>> > > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
>> > > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
>> > > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
>> > > kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
>> > > git-2.16.2.tar.gz  16-Feb-2018
>> 17:48
>> > > 7M
>> > >
>> > > Satish
>> > >
>> >
>>
>>
>


 --
 Cormac Garvey
 HPC Software Consultant
 Scientific Computing
 Idaho 

Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Garvey, Cormac T
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 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 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 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 does it still fail?
>>>
>>> module load git/2.16.2-GCCcore-5.4.0
>>>
>>> Thanks,
>>> Cormac.
>>>
>>>
>>>
>>> On Wed, Apr 4, 2018 at 4:28 PM, Kong, Fande  wrote:
>>>
 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 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 old OS [i.e old glibc etc..] - and
> this new git version [binary built locally or on a different OS and
> installed locally ?].
>
> Satish
>
> On Wed, 4 Apr 2018, Kong, Fande wrote:
>
> >  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:deskto
> p-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics
> -3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
> > Distributor ID:SUSE LINUX
> > Description:SUSE Linux Enterprise Server 11 (x86_64)
> > Release:11
> > Codename:n/a
> >
> >
> >
> > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay 
> wrote:
> >
> > > 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
> > > > 
> > > >
> > > > I gues its the OS default package
> > > >
> > > > >
> > > > Machine platform:
> > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11
> > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
> > > > Python version:
> > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
> > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
> > > > 
> > > >
> > > > What OS/version is on this machine? I can try reproducing in a VM
> > >
> > > It is strange that the kernel is old [3.0 - perhaps LTS OS] ,
> python is
> > > old [2.6] - but git is new? [2.16?]
> > >
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__
> > > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
> > > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
> > > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
> > > kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
> > > git-2.16.2.tar.gz  16-Feb-2018
> 17:48
> > > 7M
> > >
> > > Satish
> > >
> >
>
>

>>>
>>>
>>> --
>>> Cormac Garvey
>>> HPC Software Consultant
>>> Scientific Computing
>>> Idaho National Laboratory
>>> Ph: 208-526-6294
>>>
>>>
>>
>


-- 
Cormac Garvey
HPC Software Consultant
Scientific Computing
Idaho National Laboratory
Ph: 208-526-6294


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Kong, Fande
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 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 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 does it still fail?
>>
>> module load git/2.16.2-GCCcore-5.4.0
>>
>> Thanks,
>> Cormac.
>>
>>
>>
>> On Wed, Apr 4, 2018 at 4:28 PM, Kong, Fande  wrote:
>>
>>> 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 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 old OS [i.e old glibc etc..] - and
 this new git version [binary built locally or on a different OS and
 installed locally ?].

 Satish

 On Wed, 4 Apr 2018, Kong, Fande wrote:

 >  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:deskto
 p-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics
 -3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
 > Distributor ID:SUSE LINUX
 > Description:SUSE Linux Enterprise Server 11 (x86_64)
 > Release:11
 > Codename:n/a
 >
 >
 >
 > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay 
 wrote:
 >
 > > 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
 > > > 
 > > >
 > > > I gues its the OS default package
 > > >
 > > > >
 > > > Machine platform:
 > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11
 > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
 > > > Python version:
 > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
 > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
 > > > 
 > > >
 > > > What OS/version is on this machine? I can try reproducing in a VM
 > >
 > > It is strange that the kernel is old [3.0 - perhaps LTS OS] ,
 python is
 > > old [2.6] - but git is new? [2.16?]
 > >
 > > https://urldefense.proofpoint.com/v2/url?u=https-3A__
 > > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
 > > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
 > > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
 > > kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
 > > git-2.16.2.tar.gz  16-Feb-2018 17:48
 > > 7M
 > >
 > > Satish
 > >
 >


>>>
>>
>>
>> --
>> Cormac Garvey
>> HPC Software Consultant
>> Scientific Computing
>> Idaho National Laboratory
>> Ph: 208-526-6294
>>
>>
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Kong, Fande
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 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 does it still fail?
>
> module load git/2.16.2-GCCcore-5.4.0
>
> Thanks,
> Cormac.
>
>
>
> On Wed, Apr 4, 2018 at 4:28 PM, Kong, Fande  wrote:
>
>> 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 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 old OS [i.e old glibc etc..] - and
>>> this new git version [binary built locally or on a different OS and
>>> installed locally ?].
>>>
>>> Satish
>>>
>>> On Wed, 4 Apr 2018, Kong, Fande wrote:
>>>
>>> >  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:deskt
>>> op-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphic
>>> s-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
>>> > Distributor ID:SUSE LINUX
>>> > Description:SUSE Linux Enterprise Server 11 (x86_64)
>>> > Release:11
>>> > Codename:n/a
>>> >
>>> >
>>> >
>>> > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay 
>>> wrote:
>>> >
>>> > > 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
>>> > > > 
>>> > > >
>>> > > > I gues its the OS default package
>>> > > >
>>> > > > >
>>> > > > Machine platform:
>>> > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11
>>> > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
>>> > > > Python version:
>>> > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
>>> > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
>>> > > > 
>>> > > >
>>> > > > What OS/version is on this machine? I can try reproducing in a VM
>>> > >
>>> > > It is strange that the kernel is old [3.0 - perhaps LTS OS] , python
>>> is
>>> > > old [2.6] - but git is new? [2.16?]
>>> > >
>>> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__
>>> > > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
>>> > > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
>>> > > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
>>> > > kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
>>> > > git-2.16.2.tar.gz  16-Feb-2018 17:48
>>> > > 7M
>>> > >
>>> > > Satish
>>> > >
>>> >
>>>
>>>
>>
>
>
> --
> Cormac Garvey
> HPC Software Consultant
> Scientific Computing
> Idaho National Laboratory
> Ph: 208-526-6294
>
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Garvey, Cormac T
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 does it still fail?

module load git/2.16.2-GCCcore-5.4.0

Thanks,
Cormac.



On Wed, Apr 4, 2018 at 4:28 PM, Kong, Fande  wrote:

> 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 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 old OS [i.e old glibc etc..] - and
>> this new git version [binary built locally or on a different OS and
>> installed locally ?].
>>
>> Satish
>>
>> On Wed, 4 Apr 2018, Kong, Fande wrote:
>>
>> >  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:des
>> ktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:grap
>> hics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
>> > Distributor ID:SUSE LINUX
>> > Description:SUSE Linux Enterprise Server 11 (x86_64)
>> > Release:11
>> > Codename:n/a
>> >
>> >
>> >
>> > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay  wrote:
>> >
>> > > 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
>> > > > 
>> > > >
>> > > > I gues its the OS default package
>> > > >
>> > > > >
>> > > > Machine platform:
>> > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11
>> > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
>> > > > Python version:
>> > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
>> > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
>> > > > 
>> > > >
>> > > > What OS/version is on this machine? I can try reproducing in a VM
>> > >
>> > > It is strange that the kernel is old [3.0 - perhaps LTS OS] , python
>> is
>> > > old [2.6] - but git is new? [2.16?]
>> > >
>> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__
>> > > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
>> > > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
>> > > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
>> > > kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
>> > > git-2.16.2.tar.gz  16-Feb-2018 17:48
>> > > 7M
>> > >
>> > > Satish
>> > >
>> >
>>
>>
>


-- 
Cormac Garvey
HPC Software Consultant
Scientific Computing
Idaho National Laboratory
Ph: 208-526-6294


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Kong, Fande
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 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 old OS [i.e old glibc etc..] - and
> this new git version [binary built locally or on a different OS and
> installed locally ?].
>
> Satish
>
> On Wed, 4 Apr 2018, Kong, Fande wrote:
>
> >  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-noarch:graphics-2.0-amd64:graphics-2.0-noarch:
> graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:
> graphics-4.0-noarch
> > Distributor ID:SUSE LINUX
> > Description:SUSE Linux Enterprise Server 11 (x86_64)
> > Release:11
> > Codename:n/a
> >
> >
> >
> > On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay  wrote:
> >
> > > 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
> > > > 
> > > >
> > > > I gues its the OS default package
> > > >
> > > > >
> > > > Machine platform:
> > > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11
> > > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
> > > > Python version:
> > > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
> > > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
> > > > 
> > > >
> > > > What OS/version is on this machine? I can try reproducing in a VM
> > >
> > > It is strange that the kernel is old [3.0 - perhaps LTS OS] , python is
> > > old [2.6] - but git is new? [2.16?]
> > >
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__
> > > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
> > > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
> > > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
> > > kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
> > > git-2.16.2.tar.gz  16-Feb-2018 17:48
> > > 7M
> > >
> > > Satish
> > >
> >
>
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Satish Balay
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 old OS [i.e old glibc etc..] - and
this new git version [binary built locally or on a different OS and installed 
locally ?].

Satish

On Wed, 4 Apr 2018, Kong, Fande wrote:

>  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-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
> Distributor ID:SUSE LINUX
> Description:SUSE Linux Enterprise Server 11 (x86_64)
> Release:11
> Codename:n/a
> 
> 
> 
> On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay  wrote:
> 
> > 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
> > > 
> > >
> > > I gues its the OS default package
> > >
> > > >
> > > Machine platform:
> > > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11
> > 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
> > > Python version:
> > > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
> > > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
> > > 
> > >
> > > What OS/version is on this machine? I can try reproducing in a VM
> >
> > It is strange that the kernel is old [3.0 - perhaps LTS OS] , python is
> > old [2.6] - but git is new? [2.16?]
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__
> > mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
> > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
> > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
> > kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
> > git-2.16.2.tar.gz  16-Feb-2018 17:48
> > 7M
> >
> > Satish
> >
> 



Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Kong, Fande
 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-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
Distributor ID:SUSE LINUX
Description:SUSE Linux Enterprise Server 11 (x86_64)
Release:11
Codename:n/a



On Wed, Apr 4, 2018 at 4:08 PM, Satish Balay  wrote:

> 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
> > 
> >
> > I gues its the OS default package
> >
> > >
> > Machine platform:
> > ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11
> 12:30:40 UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
> > Python version:
> > 2.6.9 (unknown, Aug  5 2016, 11:15:31)
> > [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
> > 
> >
> > What OS/version is on this machine? I can try reproducing in a VM
>
> It is strange that the kernel is old [3.0 - perhaps LTS OS] , python is
> old [2.6] - but git is new? [2.16?]
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__
> mirrors.edge.kernel.org_pub_software_scm_git_=DwIBAg=
> 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00=DUUt3SRGI0_
> JgtNaS3udV68GRkgV4ts7XKfj2opmiCY=WF6ZxIh9Z9Hh2kYY0w70aNrgfPicp6
> kgIh5BvezPiEY=KWMsO7XC0-pQuQ_mD03tNJWEpxSTATlZW_DmX0QofGw=
> git-2.16.2.tar.gz  16-Feb-2018 17:48
> 7M
>
> Satish
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Satish Balay
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
> 
> 
> I gues its the OS default package
> 
> >
> Machine platform:
> ('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11 12:30:40 
> UTC 2017 (294ccfe)', 'x86_64', 'x86_64')
> Python version:
> 2.6.9 (unknown, Aug  5 2016, 11:15:31)
> [GCC 4.3.4 [gcc-4_3-branch revision 152973]]
> 
> 
> What OS/version is on this machine? I can try reproducing in a VM

It is strange that the kernel is old [3.0 - perhaps LTS OS] , python is old 
[2.6] - but git is new? [2.16?]

https://mirrors.edge.kernel.org/pub/software/scm/git/
git-2.16.2.tar.gz  16-Feb-2018 17:48  7M

Satish


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Satish Balay
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 platform:
('Linux', 'falcon1', '3.0.101-108.13-default', '#1 SMP Wed Oct 11 12:30:40 UTC 
2017 (294ccfe)', 'x86_64', 'x86_64')
Python version:
2.6.9 (unknown, Aug  5 2016, 11:15:31)
[GCC 4.3.4 [gcc-4_3-branch revision 152973]]


What OS/version is on this machine? I can try reproducing in a VM

Satish


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Satish Balay

[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.17.0.rc2
balay@asterix /home/balay


The first one is a nightlybuild testbox - and the second one is my
laptop - and I haven't seen this issue with either of them. [or any of
our other nightlybuilds - or a bugreport form any other user]

was your '2.16.2' version installed from source?

Satish

On Wed, 4 Apr 2018, Kong, Fande wrote:

> 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 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.
> >
> > Satish
> >
> 



Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Kong, Fande
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 not work:
> >
> >  petsc]$ git --version
> > git version 2.16.2
>
> Can you reproduce the error in your terminal or does it only happen
> through configure?
>

It only happens using configure.

Fande,


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Jed Brown
"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 error in your terminal or does it only happen through 
configure?


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-04-04 Thread Kong, Fande
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 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.
>
> Satish
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-03-07 Thread Satish Balay
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.

Satish


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-03-07 Thread Kong, Fande
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, in updateGitDir
> > > gitdir,err,ret = config.base.Configure.executeShellCommand([self.
> sourceControl.git,
> > > 'rev-parse','--git-dir'], cwd=self.packageDir, log = self.log)
> > >
> > >
> >
> > "#self.updateGitDir()"  works.
>
> 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.

Fande,


>
>
> diff --git a/config/BuildSystem/config/package.py
> b/config/BuildSystem/config/package.py
> index 85663247ce..439b2105c5 100644
> --- a/config/BuildSystem/config/package.py
> +++ b/config/BuildSystem/config/package.py
> @@ -516,9 +516,9 @@ class Package(config.base.Configure):
># verify that packageDir is actually a git clone
>if not os.path.isdir(os.path.join(self.packageDir,'.git')):
>  raise RuntimeError(self.packageDir +': is not a git repository!
> '+os.path.join(self.packageDir,'.git')+' not found!')
> -  gitdir,err,ret = 
> config.base.Configure.executeShellCommand([self.sourceControl.git,
> 'rev-parse','--git-dir'], cwd=self.packageDir, log = self.log)
> -  if gitdir != '.git':
> -raise RuntimeError(self.packageDir +': is not a git repository!
> "git rev-parse --gitdir" gives: '+gitdir)
> +  #gitdir,err,ret = 
> config.base.Configure.executeShellCommand([self.sourceControl.git,
> 'rev-parse','--git-dir'], cwd=self.packageDir, log = self.log)
> +  #if gitdir != '.git':
> +  #  raise RuntimeError(self.packageDir +': is not a git repository!
> "git rev-parse --gitdir" gives: '+gitdir)
>
>prefetch = 0
>if self.gitcommit.startswith('origin/'):
>
> Satish
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-03-07 Thread Satish Balay
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.executeShellCommand([self.sourceControl.git,
> > 'rev-parse','--git-dir'], cwd=self.packageDir, log = self.log)
> >
> >
> 
> "#self.updateGitDir()"  works.

I meant just the 3 lines - not the whole function.


diff --git a/config/BuildSystem/config/package.py 
b/config/BuildSystem/config/package.py
index 85663247ce..439b2105c5 100644
--- a/config/BuildSystem/config/package.py
+++ b/config/BuildSystem/config/package.py
@@ -516,9 +516,9 @@ class Package(config.base.Configure):
   # verify that packageDir is actually a git clone
   if not os.path.isdir(os.path.join(self.packageDir,'.git')):
 raise RuntimeError(self.packageDir +': is not a git repository! 
'+os.path.join(self.packageDir,'.git')+' not found!')
-  gitdir,err,ret = 
config.base.Configure.executeShellCommand([self.sourceControl.git, 
'rev-parse','--git-dir'], cwd=self.packageDir, log = self.log)
-  if gitdir != '.git':
-raise RuntimeError(self.packageDir +': is not a git repository! "git 
rev-parse --gitdir" gives: '+gitdir)
+  #gitdir,err,ret = 
config.base.Configure.executeShellCommand([self.sourceControl.git, 
'rev-parse','--git-dir'], cwd=self.packageDir, log = self.log)
+  #if gitdir != '.git':
+  #  raise RuntimeError(self.packageDir +': is not a git repository! "git 
rev-parse --gitdir" gives: '+gitdir)
 
   prefetch = 0
   if self.gitcommit.startswith('origin/'):

Satish


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-03-07 Thread Kong, Fande
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 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.executeShellCommand([self.sourceControl.git,
> 'rev-parse','--git-dir'], cwd=self.packageDir, log = self.log)
>
>

"#self.updateGitDir()"  works.

I still do not understand why.


Fande,


>
> Satish
>
> On Wed, 7 Mar 2018, Kong, Fande wrote:
>
> > [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  error still persists!
> >
> >
> > Fande,
> >
> > On Wed, Mar 7, 2018 at 12:33 PM, Satish Balay  wrote:
> >
> > > 
> > > 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/balay/petsc (next *=)
> > > $ git rev-parse --git-dir
> > > .git
> > > balay@asterix /home/balay/petsc (next *=)
> > > $ echo $?
> > > 0
> > > balay@asterix /home/balay/petsc (next *=)
> > > $
> > > <
> > >
> > > So - for some reason, git is an error in /home/kongf/workhome/projects/
> > > petsc-3.7.7/arch-linux2-c-opt-64bit/externalpackages/git.hypre
> > >
> > > You can try:
> > >
> > > cd /home/kongf/workhome/projects/petsc-3.7.7/arch-linux2-c-opt-
> > > 64bit/externalpackages/git.hypre
> > > git rev-parse --git-dir
> > > echo $?
> > > git fsck
> > >
> > > If this works - you can rerun configure and see if the error persists
> > >
> > > Satish
> > >
> > >
> > > On Wed, 7 Mar 2018, Kong, Fande wrote:
> > >
> > > > Hi PETSc team:
> > > >
> > > > What is the possible reason for this?
> > > >
> > > > The log file is attached.
> > > >
> > > >
> > > > Fande,
> > > >
> > >
> > >
> >
>
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-03-07 Thread Kong, Fande
[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  error still persists!


Fande,

On Wed, Mar 7, 2018 at 12:33 PM, Satish Balay  wrote:

> 
> 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/balay/petsc (next *=)
> $ git rev-parse --git-dir
> .git
> balay@asterix /home/balay/petsc (next *=)
> $ echo $?
> 0
> balay@asterix /home/balay/petsc (next *=)
> $
> <
>
> So - for some reason, git is an error in /home/kongf/workhome/projects/
> petsc-3.7.7/arch-linux2-c-opt-64bit/externalpackages/git.hypre
>
> You can try:
>
> cd /home/kongf/workhome/projects/petsc-3.7.7/arch-linux2-c-opt-
> 64bit/externalpackages/git.hypre
> git rev-parse --git-dir
> echo $?
> git fsck
>
> If this works - you can rerun configure and see if the error persists
>
> Satish
>
>
> On Wed, 7 Mar 2018, Kong, Fande wrote:
>
> > Hi PETSc team:
> >
> > What is the possible reason for this?
> >
> > The log file is attached.
> >
> >
> > Fande,
> >
>
>


Re: [petsc-users] Could not execute "['git', 'rev-parse', '--git-dir']"

2018-03-07 Thread Satish Balay

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/balay/petsc (next *=)
$ git rev-parse --git-dir
.git
balay@asterix /home/balay/petsc (next *=)
$ echo $?
0
balay@asterix /home/balay/petsc (next *=)
$ 
<

So - for some reason, git is an error in 
/home/kongf/workhome/projects/petsc-3.7.7/arch-linux2-c-opt-64bit/externalpackages/git.hypre

You can try:

cd 
/home/kongf/workhome/projects/petsc-3.7.7/arch-linux2-c-opt-64bit/externalpackages/git.hypre
git rev-parse --git-dir
echo $?
git fsck

If this works - you can rerun configure and see if the error persists

Satish


On Wed, 7 Mar 2018, Kong, Fande wrote:

> Hi PETSc team:
> 
> What is the possible reason for this?
> 
> The log file is attached.
> 
> 
> Fande,
>