Hung-Hsun Su <su@xxxxxxxxxxx> writes: > I do wonder what kind of effect the flag --with-mpfr has on the > installation process. I thought this was used to specify where mpfr > was installed. It is. We expect that if you build mpfr yourself, you will configure it --disable-shared, so that it is statically linked into gcc. We expect that if MPFR is installed in the system--i.e., you didn't compile it yourself--then the system will take care of ensuring that the dynamic linker can find it, e.g., via ldconfig. Embedding the location of the mpfr shared library into the binary is not a good idea by default, since it will mean that gcc will break if you copy it to a different system. That said, I think it would be reasonable to add yet another configure option to do that, for people who know they won't be copying it anywhere. It would also be entirely reasonable to use -Bstatic when linking against mpfr and gmp, on systems which have a linker which supports -Bstatic. Ian
