To switch to non-default C/C++ compiler, you need to run

./configure CC=gcc-7 CXX=g++-7

and most probably

make distclean

before starting the build

 

On Thursday, August 16, 2018 at 12:53:16 AM UTC+3, Luis Finotti wrote:
>
>
>
> On Wednesday, August 15, 2018 at 5:14:47 PM UTC-4, Dima Pasechnik wrote:
>>
>> [pip-9.0.3]   File 
>> "/usr/local/sage-8.3/local/lib/python3.6/encodings/ascii.py", line 26, in
>>  decode
>> [pip-9.0.3]     return codecs.ascii_decode(input, self.errors)[0]
>>
>> This is actually strange - why is it python3.6?
>> Are you trying to build a python3-based Sagemath?
>> (python3 support is very much work in progress in Sage)
>>
>>
>>
> No.  I just downloaded and extracted the source, did "export MAKE="make 
> -j4 -l5.5" and then "make", like I usually do.  I certainly did not try to 
> do anything different/novel.
>
>  
>
>> On Thursday, August 16, 2018 at 12:05:45 AM UTC+3, Dima Pasechnik wrote:
>>>
>>> besides it's being gcc 8.2, and AFAIK nobody ever built Sage with gcc 8, 
>>> I don't see anything strange.
>>>
>>> Not sure what data pip installer is choking on here. Hostnames with 
>>> non-ascii chars?
>>>
>>
> I don't think so:
>
> $ file /etc/hosts
> /etc/hosts: ASCII text
>
> And I don't think there is any weird directory/file name.  (At least, I 
> know not to do it.)
>
> About GCC, I have no idea when it was updated on Sid.  I have GCC 7 
> installed also.  I tried compiling with GCC 7, but it failed (maybe I did 
> not have the correct command -- I just did what "Google told me"):
>
> $ LC_ALL=C make CC=gcc-7 CPP=g++-7 CXX=g++-7 LD=g++-7
> make -j4 -l5.5 build/make/Makefile --stop
> make[1]: Entering directory '/usr/local/sage-8.3'
> rm -f config.log
> mkdir -p logs/pkgs
> ln -s logs/pkgs/config.log config.log
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make -j4 -l5.5 sets $(MAKE)... yes
> checking whether make -j4 -l5.5 supports nested variables... yes
> checking whether to enable maintainer-specific portions of Makefiles... yes
> checking for root user... no
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for ar... yes
> checking for m4... yes
> checking for ranlib... yes
> checking for strip... yes
> checking for GNU or BSD tar... /bin/tar
> checking for latex... yes
> checking for perl... /usr/bin/perl
> checking for Perl version 5.8.0 or later... yes
> checking for git... /usr/bin/X11/git
> checking for yasm... no
> checking for gcc... gcc-7
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc-7 accepts -g... yes
> checking for gcc-7 option to accept ISO C89... none needed
> checking whether gcc-7 understands -c and -o together... yes
> checking for style of include used by make -j4 -l5.5... GNU
> checking dependency style of gcc-7... none
> checking how to run the C preprocessor... g++-7
> configure: error: in `/usr/local/sage-8.3':
> configure: error: C preprocessor "g++-7" 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.
> make[1]: *** [Makefile:42: build/make/Makefile] Error 1
> make[1]: Leaving directory '/usr/local/sage-8.3'
> make: *** [Makefile:32: base-toolchain] Error 2
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to