<div dir="ltr">On Wed, Oct 1, 2014 at 9:10 AM, Jason Swails <span dir="ltr"><<a href="mailto:jason.swails@gmail.com" target="_blank">jason.swails@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I'm a new user that is trying to get Phenix installed. I'm trying the<br>
source build since I want to poke around with a little development. I<br>
haven't had much luck in this endeavor (I'm fairly competent when it<br>
comes to building especially scientific software from source).<br></blockquote><div><br></div><div>Three comments:</div><div><br></div><div>1) If you don't need the GUI, add "--no-gui" to the install arguments and it should skip most of the problematic packages.</div><div><br></div><div>2) unless I've forgotten something, the source for Phenix itself (minus third-party dependencies such as Python, wxPython, etc.) should come with all of the binary installers except for the Mac graphical package, so you might save some time by using those. Recompiling our code with modifications is not very difficult, but getting the dependencies built varies from tricky to nightmarish on some systems.</div><div><br></div><div>3) Depending on what kind of development you want to do, it may be better to work from the SVN repositories (especially CCTBX), because our code changes rather quickly and it's easy to get out of sync.</div><div><br></div><div>And a question: what exact Linux distribution and version are you running?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
What I tried was untarring the 1.9-1692 release tarball and<br>
running ./install in that directory.<br></blockquote><div><br></div><div>First recommendation: use the latest nightly, since at least one issue has already been changed.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
The first thing to fail was Imaging, and the build log complained of a<br>
missing freetype/fterrors.h header. On my machine, that file is located<br>
in /usr/include/freetype2/fterrors.h. OK, so I<br>
symlinked /usr/local/include/freetype to /usr/include/freetype2 and<br>
tried again. Imaging succeeded, but then I noticed that Phenix tried to<br>
compile its own version of freetype later (!). I'm curious as to why it<br>
would either a) not build freetype first so Imaging could use it or b)<br>
why it would try to build freetype at all when it already has to be<br>
installed.<br></blockquote><div><br></div><div>This was a bug, and I think I fixed it a few months ago.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Anyway, after that was done, I got another problem when the install<br>
process got to Pango. Then I get the error:<br>
<br>
fribidi_config.h:1:18: fatal error: glib.h: No such file or directory<br>
<br>
But glib has already been installed according to the Phenix install log<br>
(and I have it installed on my system, too). There's a glib.h in<br>
tmp/glib-2.12.11/glib/glib.h (but that directory is never added to the<br>
include search path), and also in /usr/include/glib-2.0/glib.h.<br>
I admit that the install process has me puzzled (for instance, I can't<br>
figure out how to augment CFLAGS for the Pango install to make it find<br>
glib.h), and I feel that I'm playing a bit of whack-a-mole with the<br>
build problems here...<br></blockquote><div><br></div><div>This is a little strange; in theory the headers should be available in the in-progress Phenix installation (under the directory build/$PHENIX_MTYPE/base/include, where PHENIX_MTYPE is automatically determined). For reference, the code that handles the dependency building lives here:</div><div><br></div><div><a href="http://sourceforge.net/p/cctbx/code/HEAD/tree/trunk/libtbx/auto_build/install_base_packages.py">http://sourceforge.net/p/cctbx/code/HEAD/tree/trunk/libtbx/auto_build/install_base_packages.py</a><br></div><div><br></div><div>It's quite possible I've overlooked something, although obviously this works on all of our systems.</div><div><br></div><div>-Nat</div></div></div></div>