Hi Folks, On my macbook with lion and a source code build, I always set --compiler=gcc for cctbx and this works fine. Just tried a source code build of phenix which failed because it picked up clang, so how do I override this in the install script? I didn't see the option from the install script: Graemes-MacBook-Pro:phenix-installer-dev-1078 graeme$ ./install --help Usage: install [options] Options: --prefix=<path> Determines PHENIX installation path, which will be <path > /phenix-[version] --overwrite Forces overwriting of installed packages --nproc=number Number of processors to use in compilation --base-only Do not compile PHENIX sources (cctbx, phaser, resolve, etc.) --no-gui Do not compile and install GUI components --no-apps Don't create Mac app launcher icons --app-prefix=<path> Path for Mac app launchers (default: /Applications) --noopt Turn off optimization during compilation --debug Turn on debugging during compilation --openmp Try to use OpenMP if supported by compiler --force-compile Force compilation of source --binary Force a binary install if binaries and source are both available --source Force a source install if binaries and source are both available --no-packages Do not install other packages such as PHASER --alias-mtype=<string> Force installation from a different machine type e.g. --alias-mtype=intel-linux-2.4 [for binary installations only] --try-unsupported Try source installation on an unsupported platform --help Print this help message Thanks, Graeme
On Fri, Jun 15, 2012 at 6:23 AM, Graeme Winter
On my macbook with lion and a source code build, I always set --compiler=gcc for cctbx and this works fine. Just tried a source code build of phenix which failed because it picked up clang, so how do I override this in the install script?
I don't think there's a way to do this right now, but I will investigate. Luc Bourhis had some ideas about fixing compilation on Lion which I need to follow up on anyway. I'm a little worried about what to do for all of the other packages we compile (Python, etc.); is there a possibility of incompatible libraries if they don't all use the same compiler? Aside from the technical issues - is there a reason why you can't just use the binary installer? I've been using this on Lion and have yet to see any issues. -Nat
Hi Nat,
I wanted a source code build so I could add a few things from Nick
Sauter - otherwise I would use the regular binary.
Thanks,
Graeme
On 15 June 2012 18:13, Nathaniel Echols
On Fri, Jun 15, 2012 at 6:23 AM, Graeme Winter
wrote: On my macbook with lion and a source code build, I always set --compiler=gcc for cctbx and this works fine. Just tried a source code build of phenix which failed because it picked up clang, so how do I override this in the install script?
I don't think there's a way to do this right now, but I will investigate. Luc Bourhis had some ideas about fixing compilation on Lion which I need to follow up on anyway. I'm a little worried about what to do for all of the other packages we compile (Python, etc.); is there a possibility of incompatible libraries if they don't all use the same compiler?
Aside from the technical issues - is there a reason why you can't just use the binary installer? I've been using this on Lion and have yet to see any issues.
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
On Mon, Jun 18, 2012 at 1:19 AM, Graeme Winter
I wanted a source code build so I could add a few things from Nick Sauter - otherwise I would use the regular binary.
Oh, right - forgot about that. You should probably use the separate CCTBX builds for this anyway, but I'll see if I can figure out a more universal solution. -Nat
participants (2)
-
Graeme Winter
-
Nathaniel Echols