Re: Build 0.23 gcc Version

> On Jul 28, 2015, at 6:45 AM, John Omernik wrote: > > So, I don't mean to sound like a newbie here, but in running my current setup > which has 4.6.3, (and I tried to run 4.8) how can I get Mesos 0.23 to > compile. Is this something I need to change in certain files? In certain > steps? Is t

Re: Build 0.23 gcc Version

So, I don't mean to sound like a newbie here, but in running my current setup which has 4.6.3, (and I tried to run 4.8) how can I get Mesos 0.23 to compile. Is this something I need to change in certain files? In certain steps? Is this something that should be a bug in Mesos to handle the versions?

Re: Build 0.23 gcc Version

> On Jul 24, 2015, at 3:57 PM, Michael Park wrote: > > Hi John, > > I would first suggest trying CC="gcc" CXX="g++" ../configure, and if that > works, try to find out what which cc and which c++ return and find out what > they symlink to. > I believe autotools uses cc and c++ rather than gcc

Re: Build 0.23 gcc Version

Ha, well apt-get remove gcc did not work. Now gcc gives me a not found error (even after apt-get remove gcc-4.8 and apt-get install gcc-4.8) and now my gcc --version is stuck at 4.6.3 even after apt-get remove gcc-4.8 and apt-get install gcc-4.8. Odd. On Mon, Jul 27, 2015 at 7:09 AM, John Omern

Re: Build 0.23 gcc Version

Output below with the version and the command I ran Basically I had the standard gcc installed and I added PPA for gcc 4.8 and did apt-get install. This likely left the supported official gcc there. I am a little "fresh" when it comes to dealing with this stuff, is it as simple as apt-get remove

Re: Build 0.23 gcc Version

Hi John, I would first suggest trying *CC="gcc" CXX="g++" ../configure*, and if that works, try to find out what *which* *cc* and *which* *c++* return and find out what they symlink to. I believe autotools uses *cc* and *c++* rather than *gcc* and *g++* by default, so I think there's probably some

Re: Build 0.23 gcc Version

Hey John, It appears that we're finding gcc 4.6.3 on your machine. Is it possible that your autotools are hard coded to look for a gcc that is not the gcc that you've installed and is on your path? At least for me I use devtoolset-2 and Software Collections (scl) and I can get my machine into fun

Build 0.23 gcc Version

I am trying to build 0.23, I got the error below. I already installed gcc-4.8 and set my alternatives to work with 4.8 as you can see gcc --version returns the right version, where is the configure script pulling that data? Are there flags I could use to help it through the process? :) John co