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

Satish Balay balay at mcs.anl.gov
Wed Mar 7 14:22:38 CST 2018


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/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)

Satish

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

> [kongf at falcon1 git.hypre]$ git rev-parse  --git-dir
> .git
> [kongf at falcon1 git.hypre]$ echo $?
> 0
> [kongf at falcon1 git.hypre]$
> [kongf at falcon1 git.hypre]$ git fsck
> Checking object directories: 100% (256/256), done.
> Checking objects: 100% (22710/22710), done.
> [kongf at falcon1 git.hypre]$
> 
> 
> 
> But the same  error still persists!
> 
> 
> Fande,
> 
> On Wed, Mar 7, 2018 at 12:33 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> 
> > >>>>>>>>
> > balay at 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 at asterix /home/balay
> > $ echo $?
> > 128
> > balay at asterix /home/balay
> > $ cd petsc
> > balay at asterix /home/balay/petsc (next *=)
> > $ git rev-parse --git-dir
> > .git
> > balay at asterix /home/balay/petsc (next *=)
> > $ echo $?
> > 0
> > balay at 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,
> > >
> >
> >
> 



More information about the petsc-users mailing list