I'm curious. Is my version just out of date or did my distro tamper with it? On Wed, Mar 27, 2013 at 11:32 AM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > On Wed, Mar 27, 2013 at 11:20 AM, Raymond Jennings <shentino@xxxxxxxxx> wrote: >> Here you go >> >> It seems very weird to break when an upgrade happens on a depend...so >> at this point i'm trying to find out if my distro's tampered with >> anything. > > Something is wrong. In the config.log you sent the line numbers don't > match the release. > > Looking at the of your config.log, I see that you are building > gcc-4.8.0_alpha20121216 . I thought you were building the 4.8.0 > release, but you are not. You are building a snapshot from December. > > GCC was fixed to accept cloog 0.18 on January 14, 2013. So you don't > have that patch. > > Please try using the actual 4.8.0 release, not the random snapshot you > are using. > > Ian > > > > > >> On Wed, Mar 27, 2013 at 6:17 AM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: >>> On Wed, Mar 27, 2013 at 12:22 AM, Raymond Jennings <shentino@xxxxxxxxx> wrote: >>>> On Tue, Mar 26, 2013 at 7:20 AM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: >>>>> On Mon, Mar 25, 2013 at 10:24 PM, Raymond Jennings <shentino@xxxxxxxxx> wrote: >>>>>> I'm sampling an experimental gentoo ebuild of gcc 4.8.0 and got an >>>>>> error saying that there was no "0.17" version of cloog. >>>>> >>>>> It always helps to tell us the exact error message. Thanks. >>>>> >>>>> >>>>>> However, I do have 0.18 installed. >>>>>> >>>>>> Is 0.18 just too raw to trust or is gcc deliberately avoiding it for a >>>>>> good reason? >>>>> >>>>> GCC 4.8 does accept cloog 0.18. I don't know what is going wrong. >>>> >>>> Attached is the failed build log >>> >>> Thanks. As it says at the end: >>> >>> configure: error: Unable to find a usable CLooG. See config.log for details. >>> >>> So we need to see the relevant part of the config.log file. >>> >>> Ian
