diff options
authorMatthias Maier <>2018-06-23 12:50:46 -0500
committerMatthias Maier <>2018-06-23 13:50:52 -0500
commited081df12a0fbb5ee39bb148e692a625bd8a4317 (patch)
parentNew item: Python 3.6 to become the default target (diff)
2018-06-23-mpfr-4-update: Add news item
1 files changed, 29 insertions, 0 deletions
diff --git a/2018-06-23-mpfr-4-update/2018-06-23-mpfr-4-update.en.txt b/2018-06-23-mpfr-4-update/2018-06-23-mpfr-4-update.en.txt
new file mode 100644
index 0000000..a93df9a
--- /dev/null
+++ b/2018-06-23-mpfr-4-update/2018-06-23-mpfr-4-update.en.txt
@@ -0,0 +1,29 @@
+Title: dev-libs/mpfr 4 upgrade
+Author: Matthias Maier <>
+Posted: 2018-06-23
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: <dev-libs/mpfr-4
+dev-libs/mpfr-4 introduced an ABI and soname change that has the potential
+of breaking the compiler toolchain. In order to minimize potential problems
+it is strongly recommended to rebuild mpc and gcc immediately after mpfr.
+You can do this by running
+ emerge --ask --oneshot ">=dev-libs/mpfr-4" dev-libs/mpc sys-devel/gcc
+Detailed explanation:
+ is used by (provided by dev-libs/mpc), as well as by
+internal executables (e.g. cc1, cc1plus) of sys-devel/gcc. Appropriate
+subslots in mpfr and slot-operators in dependencies in mpc and gcc will
+cause a rebuild of mpc and gcc after an upgrade of mpfr.
+However, after mpfr-4 is installed and mpc rebuiltd, but *before* gcc is
+rebuilt, gcc will be in an inconsistent state wherein symbols from
+incorrect library versions of mpfr might get used. This can result in
+segfaults and internal compiler errors. It is therefore important to
+rebuild gcc immmediately after mpc.
+A detailed update guide with troubleshoot section can be found on the wiki: