I was facing the predicament of being unable to update from gcc-4.9.3 to gcc-5.2.0, both with graphite enabled, because of the isl mismatch, i.e gcc-4.9.3 needs isl-0.12.2 while gcc-5.2.0 uses isl-0.15. To get around this block I first built gcc-5.2.0 without graphite, USE="-graphite", and the build went OK. Then I installed isl-0.15 and attempted to rebuild gcc-5.2.0 with graphite using gcc-5.2.0. Bug report #552278 states that the source has been patched to allow building gcc-5.2.0 (and gcc-4,9,3) with isl-0.15. However, the build fails. As mentioned, bug #552278 indicates that this should not happen and I was advised to file a new report. A complete build log is attached. Reproducible: Always
Created attachment 409294 [details] gcc-5.2.0 with graphite build log
hmm, looks like i queued the 5.2.0 changes, but never pushed them, and then i lost said changes in the cvs->git transition
should be fixed for real now w/5.2.0: http://sources.gentoo.org/gentoo/src/patchsets/gcc/5.2.0/gentoo/74_all_gcc5_isl-dl.patch?r1=1.1&r2=1.2 http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a515f3f02b97bc1df80a07d6b5009d2d287b1ddf
It's not fixed yet. Those patches, 74_all_gcc5_isl-dl.patch and 75_all_gcc5-isl-0.15.patch, do work, but they will NOT be applied with USE='vanilla'. The gcc-5.2.0.ebuild calls toolchain_src_prepare and this routine will NOT install any patches in the patch tarball with USE='vanilla'. Those patches should be placed in the files directory of the portage tree and the source should be patched in the ebuild with: epatch "${FILESDIR}"/all_gcc5_isl-dl.patch "${FILESDIR}"/all_gcc5-isl-0.15.patch before toolchain_src_prepare is called. Only in this way will the source be properly patched when USE='vanilla' is used.
(In reply to Frank Peters from comment #4) WAI. if you set USE=vanilla, you get the pieces.
