<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 31 Dec 2014, at 00:56, Mario Juric <<a href="mailto:mjuric@astro.washington.edu" class="">mjuric@astro.washington.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On 12/30/14 14:59 , John Swinbank wrote:<br class=""><blockquote type="cite" class="">Hello,<br class=""><br class=""><blockquote type="cite" class="">On 30 Dec 2014, at 21:31, Christoph Deil <<a href="mailto:Deil.Christoph@gmail.com" class="">Deil.Christoph@gmail.com</a>> wrote:<br class="">Now the ran into this error … the doxygen build fails with a compiler error:<br class=""><a href="https://gist.github.com/cdeil/3070715137ac799fcd41" class="">https://gist.github.com/cdeil/3070715137ac799fcd41</a><br class=""><br class="">I do have doxygen 1.8.7 from Macports at /opt/local/bin/doxygen and on my PATH, is it really useful to build a separate one from source?<br class=""></blockquote><br class="">Building Doxygen on a Mac requires that you use clang. At a guess, Macports has installed an /opt/local/bin/c++ which points to g++-mp-4.9 or similar. The Doxygen build scripts (those provided by Doxygen, not LSST) simply invoke “c++”; on your system, they’ll get GCC, and the build will fail.<br class=""><br class=""></blockquote><br class="">This is just a general comment: macports is notorious for installing<br class="">tools that shadow OS X defaults (the compiler being one of them). This<br class="">makes it very difficult to write code that builds both natively on OS X,<br class="">and on MacPorts. In effect, you're trying to build code on a system<br class="">claiming to be OS X, but whose environment is an odd mix of BSD and GNU<br class="">tools that MacPorts brought in.<br class=""><br class="">In this sense, homebrew is a _much_ more pleasant (and safer) to work<br class="">with. They're fairly careful not to shadow built-in tools, and avoid<br class="">installing software (e.g., libraries) for which native OS X version exist.<br class=""><br class="">Cheers,<br class="">-- <br class="">Mario Juric,<br class="">UW Astronomy Faculty | UW eScience | LSST DM Project Scientist<br class="">Web : <a href="http://research.majuric.org" class="">http://research.majuric.org</a> Phone : +1 609 933 1033<br class="">_______________________________________________<br class="">dm-users mailing list<br class=""><a href="mailto:dm-users@lists.lsst.org" class="">dm-users@lists.lsst.org</a><br class="">https://lists.lsst.org/mailman/listinfo/dm-users<br class=""></div></blockquote></div><div class=""><br class=""></div><div class="">After running info a few more issues on my Macbook (with and without Macports) I decided to try this Linux Docker container instead and it worked:</div><div class=""><a href="https://github.com/hepsw/docks/tree/master/cvmfs-lsst" class="">https://github.com/hepsw/docks/tree/master/cvmfs-lsst</a></div><div class=""><br class=""></div><div class="">Given the number of dependencies of the LSST software, it would be great if you could distribute a container and / or virtual machine with the latest stable version (and mention it at <a href="http://dm.lsst.org/#code" class="">http://dm.lsst.org/#code</a>).</div><div class="">It’s a bit frustrating if I have to wait for hours while boost et al. build from source before I can run `bin/demo.sh --small`.</div><div class=""><br class=""></div><div class="">Anyways, thanks for the advice with the build errors on Mac!</div><div class=""><br class=""></div><div class="">Christoph</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>