Thanks. How could you tell? I thought with gcc came with g++ by default. On Saturday, June 4, 2016 at 12:25:50 AM UTC+10, Dima Pasechnik wrote: > > > > On Friday, June 3, 2016 at 3:14:20 PM UTC+1, Dima Pasechnik wrote: >> >> Oh, I see. You need c++ compiler (g++) installed, and you do not have it. >> > > in fact > http://doc.sagemath.org/html/en/installation/source.html#prerequisites > says: > > # debian > > sudo apt-get install binutils gcc g++ gfortran make m4 perl tar git > > >> The error message could be better. >> >> On Friday, June 3, 2016 at 3:09:32 PM UTC+1, Adetokunbo Arogbonlo wrote: >>> >>> Hi Dima, >>> Here are the commands and outputs >>> ~$ which cpp >>> /usr/bin/cpp >>> >>> ~$ file /lib/cpp >>> /lib/cpp: symbolic link to /etc/alternatives/cpp >>> >>> ~$ file /etc/alternatives/cpp >>> /etc/alternatives/cpp: symbolic link to /usr/bin/cpp >>> >>> ~$ cpp -v >>> Using built-in specs. >>> COLLECT_GCC=cpp >>> Target: x86_64-linux-gnu >>> Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10' >>> ... >>> >>> >>> >>> >>> >>> >>> On Friday, June 3, 2016 at 10:46:40 PM UTC+10, Dima Pasechnik wrote: >>>> >>>> what is the output of `which cpp`? >>>> >>>> normally, /lib/cpp (what pops up in your error message) >>>> should be a symbolic link to /etc/alternatives/cpp ` like this: >>>> $ file /lib/cpp >>>> /lib/cpp: symbolic link to `/etc/alternatives/cpp' >>>> $ file /etc/alternatives/cpp >>>> /etc/alternatives/cpp: symbolic link to `/usr/bin/cpp' >>>> >>>> and now /usr/bin/cpp should exist and be what it should be >>>> $ which cpp >>>> /usr/bin/cpp >>>> $ cpp -v >>>> Using built-in specs. >>>> COLLECT_GCC=cpp >>>> Target: x86_64-linux-gnu >>>> ... >>>> >>>> >>>> >>>> On Friday, June 3, 2016 at 5:53:30 AM UTC+1, Adetokunbo Arogbonlo wrote: >>>>> >>>>> Hi, >>>>> Sagemath7.2 fails to compile from source on Debian 8.4. It gives the >>>>> following error: >>>>> >>>>> configure: error: in `/home/seyi/sage/7.2/source/sage-7.2': >>>>> configure: error: C++ preprocessor "/lib/cpp" fails sanity check >>>>> See `config.log' for more details >>>>> If you would like to try to build Sage anyway (to help porting), >>>>> export the variable 'SAGE_PORT' to something non-empty. >>>>> Makefile:24: recipe for target 'build/make/Makefile' failed >>>>> make[1]: *** [build/make/Makefile] Error 1 >>>>> make[1]: Leaving directory '/home/seyi/sage/7.2/source/sage-7.2' >>>>> Makefile:16: recipe for target 'all' failed >>>>> make: *** [all] Error 2 >>>>> >>>>> I have attached a copy of the config logs and the make logs. >>>>> Please advise men on how to proceed. >>>>> >>>>> Regards >>>>> Adetokunbo >>>>> >>>>
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
