Something that seems missing is the a whole section for actually building GCC from its sources and getting it installed. There is no such section in the manual itself. There are instuctions of course ( https://gcc.gnu.org/install/ ) but they skim over most details with little or zero explanation of such things as the wide assortment of foo_FOR_BUILD env vars and foo_FOR_TARGET that are needed to get gcc workable on some target machine. Things such as --sysroot are even more mysterious. So before I once again launch into the usual quarterly process of trying to cross build gcc for a non-native target machine are there any actual docs about those env vars or does one merely grep into the configure script and hope for the best? I am certainly able to get the configure script to do what it does[1] but the build always fails real real fast in stage1 when looking for libgmp and it seems to not matter at all that libgmp already is built and installed and works fine for the local machine and the non-native target. So is there some magic to the cross compile that is not documented much of anywhere? If the answer is "no" and go see crosstool-NG [2]then that is fine also. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional [1] https://gcc.gnu.org/ml/gcc-help/2019-02/msg00068.html [2] https://gcc.gnu.org/ml/gcc-help/2019-02/msg00092.html
