refactor: always use bundled mini-gmp#1233
Conversation
Current Aviator status
This PR was merged using Aviator.
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
|
This seems to trigger no warnings. Hopefully the LTO run wouldn't either. Since we were already compiling Therefore I suggest merging this and using mini-gmp only until igraph gains features for which an external GMP has tangible benefits. |
|
If this is merged, that's 1 out of 3 done. libxml2 should be easy too. That would leave GLPK as the only difficult one to detect. |
|
Thanks. We also need to edit Checking LTO now. |
|
@krlmlr Do you think it would be better to move defining |
|
No preference, but consistency seems important. What about the other includes that also might be misplaced? |
e34113b to
2606369
Compare
|
Will fix those in a separate commit, within this PR. Give me 5 min. |
|
Why not do this in a completely separate PR instead? |
|
Because it affects the same file, so the next PR would either depend on this, or conflict with this. Do you want me to remove that commit temporarily? |
|
Let's continue here, it's fine. If the commits are clean and self-contained, that's good enough. |
|
LTO seems fine her too. |
|
Would you like to finish the move to |
|
The move is finished in the sense that we're now consistent with the C core in what goes into |
…dor/config.h` for reasons of consistency, and to avoid confusion
87a577d to
04c7a57
Compare
This is an experiment to see if using the bundled mini-gmp triggers any warnings CRAN would complain about. I noticed that we are already compiling
mini-gmp.ceven though we were not using it.There are currently no disadvantages to using mini-gmp instead of the full-blown GMP, other than the risk of CRAN demanding source changes to fix warnings. We should not change mini-gmp ourselves it's too risky.