On 7 November 2011 17:21, Jonathan Wakely wrote:
> On 7 November 2011 17:08, Sinkler, Wharton wrote:
>> Thanks to all. I got it built successfully after setting the LD_LIBRARY_PATH environment variable in the terminal:
>>
>> export LD_LIBRARY_PATH=/usr/local/lib:${LD_LIBRARY_PATH}
>>
>> If you are interested, I am hereby volunteering to contribute a short writeup of the successful installation process on my system. I think this could be helpful to people wanting to install gcc, but not as versed in Unix and working with compilers and linkers.
>>
>> One thing which I would recommend is to put links on the installation pages (http://gcc.gnu.org/install/) to some of FAQ and tutorial pages.
>>
>> Let me know if you would entertain my editing of the html files and emailing these back your way.
>
> Feel free to edit the wiki, but I'm curious what could be explained in
> simpler terms than http://advogato.org/person/redi/diary/253.html
>
> (less patronising terms, maybe, but what about those instructions is not clear?)
>
N.B. having to set LD_LIBRARY_PATH is ***not*** a good solution, and I
hope any writeup which suggests doing that will be rejected. The
simplest solution is to install GCC from pre-built packages from
someone who knows what they're doing, the next best is to link to gmp,
mpfr and mpc statically so LD_LIBRARY_PATH is not needed.
The worst, least reliable method is to require LD_LIBRARY_PATH to be
set when running the compiler.
Unfortunately everyone who tries to build the compiler thinks that
installing gmp, mpfr and mpc in /some/path/to/libs is a good idea,
then gets stuck, then discovers that LD_LIBRARY_PATH unsticks them,
and thinks that's a good solution.
