Hi Ethan,
build logs are in:
$HOME/public_html/build-logs/
... some subdirectory depending on computer name, OS, etc.
This will give you some hints where it stopped (and why). Otherwise
manual continuation is of course possible (providing everything else got
correctly compiled and installed), but you may want to pass some more
information to configure (check config.log - if there - or the autobuild
script for flags). But then the usual: make, make install
B
On 06/02/2013 02:11, Ethan Merritt wrote:
Since the pdbe has apparently changed its URL, breaking the download
capability in the version of coot I've been running, I decided to try
to build a current copy from source.
I downloaded the autobuild.sh script,
customized AUTOBUILD_BUILD and AUTOBUILD_INSTALLED,
stuck a #!/bin/bash at the top, and ran
./autobuild.sh python
It downloaded and built lots of support libraries but not,
unfortunately, coot itself.
The last thing output by the script was
Connecting to www2.mrc-lmb.cam.ac.uk
(www2.mrc-lmb.cam.ac.uk)|131.111.85.100|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16160810 (15M) [application/x-tar]
Server file no newer than local file
“/home/local/coot/autobuild/sources/coot-0.7.1-pre-revision-4552.tar.gz” -- not
retrieving.
I can't find any error messages
or log files. All I know is that the autobuild process seems to have
stopped at that point and not built an executable.
Is there some follow-on command I need to run?
Do I need to manually ./configure and make in a subdirectory?
Ethan
--
***************************************************
Dr. Bernhard Lohkamp
Assistant Professor
Div. Molecular Structural Biology
Dept. of Medical Biochemistry and Biophysics (MBB)
Karolinska Institutet
S-17177 Stockholm
Sweden
phone: (+46) 08-52487651
fax: (+46) 08-327626
email: [email protected]
