Ah ok. configure currently doesn't handle a change in 'giturl' well. [currently requires us to delete the current externalpackages/git.p4est repo and rerun configure]
perhaps there is a simple way to fix this. [check 'url' in .git/config - and change it if needed - or do a 'git fetch url' or someting else]. Satish On Mon, 13 Feb 2017, Tobin Isaac wrote: > Hi Mark, > > Sorry for the delay. Now that there is an official p4est release that > can be used in petsc, I switch the repo back to the official repo. I > think you're getting an error because my development repo didn't have > v2.0, but i just fixed that, to make it easier to hop back and forth > between branches. > > Toby > > On Sat, Feb 11, 2017 at 08:04:20AM -0500, Mark Adams wrote: > > I am getting this in master: > > > > ******************************************************************************* > > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for > > details): > > ------------------------------------------------------------------------------- > > Unable to locate commit: v2.0 in repository: > > /Users/markadams/Codes/petsc/arch-macosx-gnu-g/externalpackages/git.p4est. > > If its a remote branch- use: origin/v2.0 > > >
