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 this something that should be a bug in Mesos to handle the > versions? Is this a configuration issue? I'd love to learn more about how > this works, but would love some pointers here, and since my setup is fairly > vanilla, others may also benefit from getting this to work. AFAIK mesos requires gcc >= 4.8. You can force a specific compiler by setting the CC and CXX variables to configure, eg. ./configure CC=gcc-4.8 CXX=g++-4.8. In your previous message, it looked like configure was using cached values for the compiler check. If it still does that try removing config.cache. > > > John > > On Mon, Jul 27, 2015 at 10:56 AM, James Peach wrote: > > > 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 and g++ by default, so > > I think there's probably something funky going on there. > > No, you explicitly tell autoconf to default to G++ > > mesos.git jpeach$ grep AC_PROG_C configure.ac > AC_PROG_CXX([g++]) > AC_PROG_CC([gcc]) > > IMHO the correct invocation is something like: > AC_PROG_CXX([c++ g++ clang++]) > > since you should always default to the system default toolchain > > J > >
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? Is this a configuration issue? I'd love to learn more about how this works, but would love some pointers here, and since my setup is fairly vanilla, others may also benefit from getting this to work. John On Mon, Jul 27, 2015 at 10:56 AM, James Peach wrote: > > > 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 and g++ by default, > so I think there's probably something funky going on there. > > No, you explicitly tell autoconf to default to G++ > > mesos.git jpeach$ grep AC_PROG_C configure.ac > AC_PROG_CXX([g++]) > AC_PROG_CC([gcc]) > > IMHO the correct invocation is something like: > AC_PROG_CXX([c++ g++ clang++]) > > since you should always default to the system default toolchain > > J > >
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 and g++ by default, so I > think there's probably something funky going on there. No, you explicitly tell autoconf to default to G++ mesos.git jpeach$ grep AC_PROG_C configure.ac AC_PROG_CXX([g++]) AC_PROG_CC([gcc]) IMHO the correct invocation is something like: AC_PROG_CXX([c++ g++ clang++]) since you should always default to the system default toolchain J
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 Omernik wrote: > 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 gcc? > > > > > > configure: creating ./config.lt > > config.lt: creating libtool > > configure: Setting up build environment for x86_64 linux-gnu > > checking whether we are using the GNU C++ compiler... (cached) yes > > checking whether g++ accepts -g... (cached) yes > > checking dependency style of g++... (cached) gcc3 > > checking whether we are using the GNU C compiler... (cached) yes > > checking whether gcc accepts -g... (cached) yes > > checking for gcc option to accept ISO C89... (cached) none needed > > checking whether gcc understands -c and -o together... (cached) yes > > checking dependency style of gcc... (cached) gcc3 > > checking for C++ compiler vendor... gnu > > checking for C++ compiler version... 4.6.3 > > checking for C++ compiler vendor... (cached) gnu > > configure: error: GCC 4.8 or higher required (found 4.6.3) > > darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version > > gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 > > Copyright (C) 2013 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > > darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ CC="gcc" > CXX="g++" ../configure > > On Fri, Jul 24, 2015 at 5: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* and *g++* by >> default, so I think there's probably something funky going on there. >> >> MPark. >> >> On Fri, Jul 24, 2015 at 2:31 PM Benjamin Hindman < >> benjamin.hind...@gmail.com> wrote: >> >>> 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 funky set ups where I've got a gcc 4.8 installed >>> but using autotools it picks the wrong compiler. >>> >>> Ben. >>> >>> On Fri, Jul 24, 2015 at 2:02 PM John Omernik wrote: >>> 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 configure: error: GCC 4.8 or higher required (found 4.6.3) darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >>> >
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 gcc? configure: creating ./config.lt config.lt: creating libtool configure: Setting up build environment for x86_64 linux-gnu checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking for C++ compiler vendor... gnu checking for C++ compiler version... 4.6.3 checking for C++ compiler vendor... (cached) gnu configure: error: GCC 4.8 or higher required (found 4.6.3) darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ CC="gcc" CXX="g++" ../configure On Fri, Jul 24, 2015 at 5: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* and *g++* by > default, so I think there's probably something funky going on there. > > MPark. > > On Fri, Jul 24, 2015 at 2:31 PM Benjamin Hindman < > benjamin.hind...@gmail.com> wrote: > >> 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 funky set ups where I've got a gcc 4.8 installed >> but using autotools it picks the wrong compiler. >> >> Ben. >> >> On Fri, Jul 24, 2015 at 2:02 PM John Omernik wrote: >> >>> 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 >>> >>> >>> >>> configure: error: GCC 4.8 or higher required (found 4.6.3) >>> >>> darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version >>> >>> gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 >>> >>> Copyright (C) 2013 Free Software Foundation, Inc. >>> >>> This is free software; see the source for copying conditions. There is >>> NO >>> >>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >>> PURPOSE. >>> >>
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 something funky going on there. MPark. On Fri, Jul 24, 2015 at 2:31 PM Benjamin Hindman wrote: > 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 funky set ups where I've got a gcc 4.8 installed > but using autotools it picks the wrong compiler. > > Ben. > > On Fri, Jul 24, 2015 at 2:02 PM John Omernik wrote: > >> 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 >> >> >> >> configure: error: GCC 4.8 or higher required (found 4.6.3) >> >> darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version >> >> gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 >> >> Copyright (C) 2013 Free Software Foundation, Inc. >> >> This is free software; see the source for copying conditions. There is NO >> >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> >
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 funky set ups where I've got a gcc 4.8 installed but using autotools it picks the wrong compiler. Ben. On Fri, Jul 24, 2015 at 2:02 PM John Omernik wrote: > 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 > > > > configure: error: GCC 4.8 or higher required (found 4.6.3) > > darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version > > gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 > > Copyright (C) 2013 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >
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 configure: error: GCC 4.8 or higher required (found 4.6.3) darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
