Added documentation for Building GCC and Useful Aliases and Scripts. #4
Conversation
| @@ -0,0 +1,255 @@ | |||
| Aliases and Scripts | |||
| =================== | |||
|
|
|||
There was a problem hiding this comment.
Can you split out aliases-and-scripts into a separate pull request, please.
There was a problem hiding this comment.
FWIW the aliases and scripts material seems less universal to me, more your personal setup. My feeling is that it makes more sense as an appendix compared to the other material.
how-to-build-gcc-from-source.rst
Outdated
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| GCC has a script called ``configure`` inside the source directory at | ||
| ``~/gcc/configure``. Calling by itself will enable every option by default. |
There was a problem hiding this comment.
Does it really "enable every option by default" ? IIRC it picks defaults for every option, which is somewhat different.
| --disable-libcc1 --disable-libstdcxx-pch --disable-libssp --disable-isl \ | ||
| --disable-libmpx --disable-libsanitizer --disable-libquadmath \ | ||
| --disable-libatomic | ||
|
|
There was a problem hiding this comment.
I like to configure with "--enable-valgrind-annotations", but that may be just me
There was a problem hiding this comment.
FWIW I also like to set a --prefix for where the built gcc should be installed to, setting it to a sibling directory of the build directory, so that it can be installed without needing sudo.
| messages to console when compiling. The ``-Iinclude`` option lets you | ||
| compile code that contains ``#include``'s when using | ||
| either ``cc1`` or ``cc1plus``. | ||
|
|
There was a problem hiding this comment.
Rather than invoke cc1plus directly, I tend to use "./xgcc" and "./xg++"
Hello,
I've added documentation on Building GCC from source, as well as a page for useful aliases and scripts that would be used frequently during development. Let me know if anything should be changed or added!
Thank you,
Matthew Beliveau