librelist archives

« back to archive

Update the develop branch of p4est.

Update the develop branch of p4est.

From:
Ethan Hereth
Date:
2014-09-19 @ 18:13
Hey all,

I just did a fetch of the repo from github and am trying to build the
develop branch. when I run 'git submodule update' I get the following
error:

fatal: reference is not a tree: 6d24c6794e84112a7436aa5b83347c3479abf153
Unable to checkout '6d24c6794e84112a7436aa5b83347c3479abf153' in
submodule path 'sc'

It appears as if that commit hasn't been pushed to the remote at:

http://burstedde.ins.uni-bonn.de/repos/libsc.git

That particular commit has been pushed to github. Is there a reason
that the sc submodule points to the repo listed above in lieu of
github? Just wondering.

Another, unrelated question. Is it necessary that the autotools find a
working/usable fortran77 compiler? My system must be a little messed
up because every time I try to re-compile the project I have to mess
around with the F77 environment variable until I find a version that
configure likes. Since this is a C only project is it even necessary
that a working version of f77 be found? Please be kind, I am quite
unfamiliar with using the autotools and usually if they don't just
work out of the box I am out of luck!

Thanks!

Ethan Alan

Re: [p4est] Update the develop branch of p4est.

From:
Carsten Burstedde
Date:
2014-09-20 @ 11:24
> I just did a fetch of the repo from github and am trying to build the
> develop branch. when I run 'git submodule update' I get the following
> error:
> 
> fatal: reference is not a tree: 6d24c6794e84112a7436aa5b83347c3479abf153
> Unable to checkout '6d24c6794e84112a7436aa5b83347c3479abf153' in
> submodule path 'sc'
> 
> It appears as if that commit hasn't been pushed to the remote at:
> 
> http://burstedde.ins.uni-bonn.de/repos/libsc.git
> 
> That particular commit has been pushed to github. Is there a reason
> that the sc submodule points to the repo listed above in lieu of
> github? Just wondering.

That repo is usually somewhat behind in history.  A fresh clone should
refer to the sc repository on github.  Did Alex's hint do the trick?
There's also git submodule update --init.

> Another, unrelated question. Is it necessary that the autotools find a
> working/usable fortran77 compiler? My system must be a little messed
> up because every time I try to re-compile the project I have to mess
> around with the F77 environment variable until I find a version that
> configure likes. Since this is a C only project is it even necessary
> that a working version of f77 be found? Please be kind, I am quite
> unfamiliar with using the autotools and usually if they don't just
> work out of the box I am out of luck!

How's p4est's configure --without-blas working for you?

Carsten

Re: [p4est] Update the develop branch of p4est.

From:
Ethan Hereth
Date:
2014-09-20 @ 19:28
On Sat, Sep 20, 2014 at 7:24 AM, Carsten Burstedde
<burstedde@ins.uni-bonn.de> wrote:
>> I just did a fetch of the repo from github and am trying to build the
>> develop branch. when I run 'git submodule update' I get the following
>> error:
>>
>> fatal: reference is not a tree: 6d24c6794e84112a7436aa5b83347c3479abf153
>> Unable to checkout '6d24c6794e84112a7436aa5b83347c3479abf153' in
>> submodule path 'sc'
>>
>> It appears as if that commit hasn't been pushed to the remote at:
>>
>> http://burstedde.ins.uni-bonn.de/repos/libsc.git
>>
>> That particular commit has been pushed to github. Is there a reason
>> that the sc submodule points to the repo listed above in lieu of
>> github? Just wondering.
>
> That repo is usually somewhat behind in history.  A fresh clone should
> refer to the sc repository on github.  Did Alex's hint do the trick?
> There's also git submodule update --init.

Alex's hint did do the trick. Thank you Alex!
>
>> Another, unrelated question. Is it necessary that the autotools find a
>> working/usable fortran77 compiler? My system must be a little messed
>> up because every time I try to re-compile the project I have to mess
>> around with the F77 environment variable until I find a version that
>> configure likes. Since this is a C only project is it even necessary
>> that a working version of f77 be found? Please be kind, I am quite
>> unfamiliar with using the autotools and usually if they don't just
>> work out of the box I am out of luck!
>
> How's p4est's configure --without-blas working for you?.

The command

../configure --enable-mpi CC=/usr/local/openmpi-1.6.1-gcc/bin/mpicc
CXX=/usr/local/openmpi-1.6.1-gcc/bin/mpic++ CFLAGS="-O3"
--without-blas

Still looks for an f77 compiler. For some reason on my system the
default compiler if finds cannot make an executable... This is the
error I get:

checking whether the Fortran 77 compiler works... no
configure: error: in `/home/ehereth/Codes/p4est/build':
configure: error: Fortran 77 compiler cannot create executables

This is really not a big deal anymore. I have figured out how to get
it to compile and have made a note for the future. I was just curious
as to why that compiler was even necessary as this is a C only
project. Toby cleared that up though.

I appreciate it everyone!

Ethan Alan

>
> Carsten

Re: [p4est] Update the develop branch of p4est.

From:
Tobin Isaac
Date:
2014-09-19 @ 19:34
On Fri, Sep 19, 2014 at 02:13:46PM -0400, Ethan Hereth wrote:
> Hey all,
> 
> I just did a fetch of the repo from github and am trying to build the
> develop branch. when I run 'git submodule update' I get the following
> error:
> 
> fatal: reference is not a tree: 6d24c6794e84112a7436aa5b83347c3479abf153
> Unable to checkout '6d24c6794e84112a7436aa5b83347c3479abf153' in
> submodule path 'sc'
> 
> It appears as if that commit hasn't been pushed to the remote at:
> 
> http://burstedde.ins.uni-bonn.de/repos/libsc.git
> 
> That particular commit has been pushed to github. Is there a reason
> that the sc submodule points to the repo listed above in lieu of
> github? Just wondering.

We have been making github the default distribution point, but the
.gitmodules file may not have been updated.  Thanks for bringing this
to our attention.

> 
> Another, unrelated question. Is it necessary that the autotools find a
> working/usable fortran77 compiler? My system must be a little messed
> up because every time I try to re-compile the project I have to mess
> around with the F77 environment variable until I find a version that
> configure likes. Since this is a C only project is it even necessary
> that a working version of f77 be found? Please be kind, I am quite
> unfamiliar with using the autotools and usually if they don't just
> work out of the box I am out of luck!

We have fortran configuration logic because the libsc modules has some
blas/lapack dependent functionality.  But as p4est is an essentially
floating-point free package, it may be possible to modify the
configuration to avoid the issue.  Carsten is more knowledgeable about
this, so I will defer to him on this.

Regards,
  Toby

> 
> Thanks!
> 
> Ethan Alan
> 

Re: [p4est] Update the develop branch of p4est.

From:
Alex Fikl
Date:
2014-09-19 @ 19:28
Hello,

To solve the problem with git submodule, you can try executing:
git submodule sync

The problem is that the url for the libsc repository changed a few
months ago, and a simple "git submodule update" doesn't update the url
in your local clone. If that doesn't work for some reason, you can
always manually modify the remote url for libsc in p4est/.git/config.
Hope that helped!

Alex

On Fri, Sep 19, 2014 at 8:13 PM, Ethan Hereth
<advocateddrummer@gmail.com> wrote:
> Hey all,
>
> I just did a fetch of the repo from github and am trying to build the
> develop branch. when I run 'git submodule update' I get the following
> error:
>
> fatal: reference is not a tree: 6d24c6794e84112a7436aa5b83347c3479abf153
> Unable to checkout '6d24c6794e84112a7436aa5b83347c3479abf153' in
> submodule path 'sc'
>
> It appears as if that commit hasn't been pushed to the remote at:
>
> http://burstedde.ins.uni-bonn.de/repos/libsc.git
>
> That particular commit has been pushed to github. Is there a reason
> that the sc submodule points to the repo listed above in lieu of
> github? Just wondering.
>
> Another, unrelated question. Is it necessary that the autotools find a
> working/usable fortran77 compiler? My system must be a little messed
> up because every time I try to re-compile the project I have to mess
> around with the F77 environment variable until I find a version that
> configure likes. Since this is a C only project is it even necessary
> that a working version of f77 be found? Please be kind, I am quite
> unfamiliar with using the autotools and usually if they don't just
> work out of the box I am out of luck!
>
> Thanks!
>
> Ethan Alan