On 8 Dec 2015 17:48, "Vincent Delecroix" <20100.delecr...@gmail.com> wrote:
>
> Try "make distclean" (there is no "-").
>

Ok, I'm not sure if i did that so will try.  Ubuntu.

>
> On 08/12/15 14:43, John Cremona wrote:
>>
>> I gave up trying to build a newly updated (from 6.9 to 6.10.beta7)
>> Sage from source since I got so many errors.  Even "make dist-clean"
>> fails as follows:
>>
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make dist-clean'):
>>
>> * package: backports_ssl_match_hostname-3.4.0.2
>>    log file:
/home/jec/sage/logs/pkgs/backports_ssl_match_hostname-3.4.0.2.log
>>    build directory:
>>
/home/jec/sage/local/var/tmp/sage/build/backports_ssl_match_hostname-3.4.0.2
>>
>> * package: certifi-14.05.14
>>    log file: /home/jec/sage/logs/pkgs/certifi-14.05.14.log
>>    build directory:
/home/jec/sage/local/var/tmp/sage/build/certifi-14.05.14
>>
>> * package: decorator-4.0.2
>>    log file: /home/jec/sage/logs/pkgs/decorator-4.0.2.log
>>    build directory:
/home/jec/sage/local/var/tmp/sage/build/decorator-4.0.2
>>
>> * package: jsonschema-2.4.0
>>    log file: /home/jec/sage/logs/pkgs/jsonschema-2.4.0.log
>>    build directory:
/home/jec/sage/local/var/tmp/sage/build/jsonschema-2.4.0
>>
>> * package: markupsafe-0.23
>>    log file: /home/jec/sage/logs/pkgs/markupsafe-0.23.log
>>    build directory:
/home/jec/sage/local/var/tmp/sage/build/markupsafe-0.23
>>
>> * package: setuptools_scm-1.7.0
>>    log file: /home/jec/sage/logs/pkgs/setuptools_scm-1.7.0.log
>>    build directory:
/home/jec/sage/local/var/tmp/sage/build/setuptools_scm-1.7.0
>>
>> * package: six-1.9.0
>>    log file: /home/jec/sage/logs/pkgs/six-1.9.0.log
>>    build directory: /home/jec/sage/local/var/tmp/sage/build/six-1.9.0
>>
>> The build directory may contain configuration files and other potentially
>> helpful information. WARNING: if you now run 'make' again, the build
>> directory will, by default, be deleted. Set the environment variable
>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>
>> If I cannot even make dist-clean, what can I do?  I have no idea how
>> this situation was reached.  Should I just delete the entire directory
>> and start again?
>>
>> This is the reward I get for not building any versions of Sage for a
>> month or two and then trying to fix a bug!
>>
>> John
>>
>
> --
> 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 http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to