[COOT] Ubuntu Jaunty (9.04) subversion build works great now

[hari jayaram]

Hello Paul and everyone,
Since I had complained about difficulties in building coot from subersion on
Ubuntu Jaunty , I  thought I should write in to say that I tried building
the subversion revision 2021 on ubuntu 9.04 from scratch and it builds just
fine and everything works great

However the build-it-gtk2-simple python build script seems to always build
into two directories
the :
$AUTOBUILD_BUILD/coot-pre-release-gtk2-python
AND
$AUTOBUILD_BUILD/coot-Linux-i686-ubuntu-9.04-gtk2-python

For my 32 bit 9.04 running ubuntu the coot-pre-release-gtk2-python/bin/coot
binary works just fine .

The coot-Linux-i686-ubuntu-9.04-gtk2-python/bin/coot stops with a message
(GThread-ERROR **: GThread system may only be initialized once.). Is that
because it may be a 64 bit build?

So I am guessing I have to give some command line switch to the script to
suppress the i686 build on this ubuntu 32bit 9.04 box.

Regardless I am happily cooting with the latest build on Jaunty jackalope.
Thanks a tonne
Hari


On Tue, May 12, 2009 at 11:11 AM, hari jayaram hari...@gmail.com wrote:

 Hello ,
 The jaunty 32 bit build seems to fail ( with subversion revision 2002 as
 well)
 It seems like based on what Ed Pozharsky wrote in ..its a problem with
 guile
 in Ubuntu jaunty (9.04) ..

 On my 32 bit , 9.04 installation , the build-it-gtk2-simple script chugs
 along fine and then declares the following contradictory message

 checking for Clipper... yes
 Congratulations, you are using Guile
 checking for guile... no
 configure: error: guile required but not found

 Regardless ..I will try Bill Scots or the CCP4 wiki  
 methodhttp://strucbio.biologie.uni-konstanz.de/ccp4wiki/index.php/Custom_building_Coot_from_source_codeof
  separately compiling all the coot dependencies . But though I would wrote
 in to inquire if there was already a simpler fix.

 Thanks

 Hari



 On Fri, May 8, 2009 at 7:35 PM, Paul Emsley paul.ems...@bioch.ox.ac.ukwrote:

 hari jayaram wrote:

 Hi ..I tried a coot subversion (revision 1994) built-it-simple python on
 the newest ubuntu 9.04

 The build crashes just after it builds guile and ( 16-coot.txt in the
 build directory ) reads :

 checking for Clipper... yes
 Congratulations, you are using Guile
 checking for guile... no
 configure: error: guile required but not found
 ./build-it-gtk2-simple: line 2742: [: =: unary operator expected
 NO need to update libtool
 /home/hari/autobuild/ex-charlie_2009-05-08__T20_14_49/coot-0.6-pre-1
 make: *** No targets specified and no makefile found.  Stop.

 This happens only on the new ubuntu (on a 32 bit 9.04 system) .
 I was able to build this revision without any problem on Ubuntu 8.04 64
 bit


 Thanks update_libtool is not set sometimes, so using it as in 1994 is
 wrong.  I've tweaked the script.

 But the problem for you lies above that..
  checking for guile... no
  configure: error: guile required but not found

 Hmm!  what went wrong there..?

 I'll try to build from scratch on Jaunty myself.

 Cheers,

 Paul.

Re: [COOT] Ubuntu Jaunty (9.04) subversion build works great now

[Paul Emsley]

hari jayaram wrote:

Hello Paul and everyone,
Since I had complained about difficulties in building coot from 
subersion on Ubuntu Jaunty , I  thought I should write in to say that I 
tried building the subversion revision 2021 on ubuntu 9.04 from scratch 
and it builds just fine and everything works great


2021 has interactive sharpening - enjoy :)



However the build-it-gtk2-simple python build script seems to always 
build into two directories

the :
$AUTOBUILD_BUILD/coot-pre-release-gtk2-python
AND
$AUTOBUILD_BUILD/coot-Linux-i686-ubuntu-9.04-gtk2-python


Technical answer: IIUC, the build script builds coot and dependences and 
dev files in $AUTOBUILD_BUILD/coot-pre-release-gtk2-python.  At the end 
the build script copies (rsyncs) out a minimal portion the built files. 
 You don't need the include files to run coot (this cuts down the 
binary tar ball size and was suggested by Clemens Vonrhein).  Being in a 
different directory to the one in which it was built simulates being 
installed on another computer - and thus we (also) run the test suite 
from there (which has caught a few problems in the past).



 
For my 32 bit 9.04 running ubuntu the 
coot-pre-release-gtk2-python/bin/coot binary works just fine .


Good.



The coot-Linux-i686-ubuntu-9.04-gtk2-python/bin/coot stops with a 
message (GThread-ERROR **: GThread system may only be initialized 
once.). Is that because it may be a 64 bit build?


No, well, not fundamentally - it seems to me that a bug is being tickled 
but only in the 64 bit version.


I wonder (to myself) if it is because both scheme and python are setting 
up threads...


So I am guessing I have to give some command line switch to the script 
to suppress the i686 build on this ubuntu 32bit 9.04 box.


No... not really... (i686 is the default, isn't it?) you can set the 
arch type in the compiler flags if you want, but that is not a proper 
solution.




Regardless I am happily cooting with the latest build on Jaunty jackalope.
Thanks a tonne


:-)

Paul.