https://svn.boost.org/trac10/ticket/3228 <p> I would like to propose a usability fix to the Getting Started Guide at the following location. </p> <p> <a href="http://www.boost.org/doc/libs/1_39_0/more/getting_started/unix-variants.html#id27">http://www.boost.org/doc/libs/1_39_0/more/getting_started/unix-variants.html#id27</a> </p> <p> "Select your configuration options and invoke ./bootstrap.sh again without the --help option. Unless you have write permission in your system's /usr/local/ directory, you'll probably want to at least use" </p> <p> BEFORE $ ./bootstrap.sh --prefix=path/to/installation/prefix PROPOSED FIXED $ ./bootstrap.sh --prefix=path/to/installation/prefix --exec-prefix=path/to/installation/prefix </p> <p> "--exec-prefix" is needed to make sure that the libs can go where you want too - they default to the /lib dir which is not writeable by most people. </p> <p> Thanks again! </p> <p> --- </p> <p> REFERENCE Installation directories: </p> <blockquote> <p> --prefix=PREFIX install Boost into the given PREFIX </p> <blockquote> <p> <a href="https://svn.boost.org/trac10/usr/local">usr/local</a> </p> </blockquote> <p> --exec-prefix=EPREFIX install Boost binaries into the given EPREFIX </p> <blockquote> <p> [PREFIX] </p> </blockquote> </blockquote> <p> More precise control over installation directories: </p> <blockquote> <p> --libdir=DIR install libraries here [EPREFIX/lib] --includedir=DIR install headers here [PREFIX/include] </p> </blockquote> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/3228 Trac 1.4.3 Dave Abrahams Sun, 28 Jun 2009 05:50:57 GMT https://svn.boost.org/trac10/ticket/3228#comment:1 https://svn.boost.org/trac10/ticket/3228#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">invalid</span> </li> </ul> <p> As far as I can tell, the default exec-prefix is the same as the prefix, so telling people to set the prefix to a writable directory handles that problem. I think this complication of the directions is not necessary. If I am wrong and the directions don't work, please reopen and reassign this ticket to vladimir_prus, who is responsible for bootstrap.sh </p> Ticket