| Summary: | gcc 4.8/4.9 flto mismatch causes r-base CRAN packages not to compile | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Joseph Wang <joequant> |
| Component: | RPM Packages | Assignee: | Luc Menut <lmenut> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | Keywords: | Triaged |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | R-base | CVE: | |
| Status comment: | |||
It looks like R-base won't build with gcc 4.9 at all with LTO turned on. Switching it off.
Manuel Hiebel
2014-06-17 22:48:18 CEST
Keywords:
(none) =>
Triaged Fixed by disabling lto, which is the default upstream. Keywords:
NEEDINFO =>
(none) |
install.packages('httpuv') fails with R-base 3.0.3-1. The problem appears to be that R-base was built with 4.8. Building source CRAN files with R-base after gcc 4.9 sets the -flto flag which generates lto files that seem to be incompatible with earlier versions of R built with 4.8 One solution is to change the /etc/makeconf for R to LTO="-flto ffat-lto-objects" However, another solution is to rebuild R-base with gcc > 4.9