diff options
| author | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2011-08-15 11:56:39 +0000 |
|---|---|---|
| committer | vlefevre <vlefevre@280ebfd0-de03-0410-8827-d642c229c3f4> | 2011-08-15 11:56:39 +0000 |
| commit | 25a0928ae3c27319c3001dcf49451b3578af19e6 (patch) | |
| tree | 4650769d28afb4d1fafca73e3183793d3815e276 | |
| parent | 0af8125a26208dfb7958d9cb9e58f4f84ac84a43 (diff) | |
| download | mpfr-25a0928ae3c27319c3001dcf49451b3578af19e6.tar.gz | |
FAQ update with update-faq.
git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/branches/3.0@7799 280ebfd0-de03-0410-8827-d642c229c3f4
| -rw-r--r-- | FAQ.html | 8 |
1 files changed, 6 insertions, 2 deletions
@@ -213,8 +213,12 @@ the <cite><acronym>GMP</acronym></cite> library could not be found (as it is not in the provided library search paths) or because the <cite><acronym>GMP</acronym></cite> library that was found does not have the expected <acronym title="Application Binary Interface">ABI</acronym> -(<abbr>e.g.</abbr> 32-bit <abbr>vs</abbr> 64-bit). The latter problem can -have several causes:</p> +(<abbr>e.g.</abbr> 32-bit <abbr>vs</abbr> 64-bit). The former problem can be +due to the fact that a static build of <cite><acronym>MPFR</acronym></cite> +was requested while only a shared <cite><acronym>GMP</acronym></cite> library +is installed (or the opposite, but another error can also show up in this +case, see the <a href="#fpic">question about <samp>-fPIC</samp></a>). The +latter problem can have several causes:</p> <ul> <li>A wrong libgmp library has been picked up. This can occur if you have several <cite><acronym>GMP</acronym></cite> versions installed on the |