Sage 6.6.rc2 released

[Volker Braun]

As usual, get the "develop" branch or the source tarball from http://www.sagemath.org/download-latest.html

819000f Updated Sage version to 6.6.rc2

5e10512 Trac #18064: sage_doc crashes on cached_function when __doc__ is empty

e457d1a Trac #17996: Missing Source in numerical_approx??

6c80105 Trac #18091: symbolic floor,ceil,factorial need _evalf_ too

80f019f Trac #14196: "subgroups" fails for C1 x C2

87b2e73 Trac #18073: banner: Sage --> SageMath

34c2c64 Trac #17913: Out of memory reinstalling webassets

4087964 Updated Sage version to 6.6.rc1

[John Cremona]

I built 6.6.rc2 fine on one machine, but building it again on the same
machine (different directory) I had an error building libgd:

libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I/home/lmfdb/sage2/local/include/libpng12 -I/home/lmfdb/s
age/local/include/freetype2 -g -fvisibility=hidden -MT gdft.lo -MD -MP
-MF .deps/gdft.Tpo -c gdft.c -fPIC -DPIC
-o .libs/gdft.o
gdft.c:153:22: fatal error: ft2build.h: No such file or directory
#include <ft2build.h>
^
compilation terminated.

Nothing on that machine changed between these two builds.

John

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

[Francois Bissey]

What does PKG_CONFIG_PATH says?

François

[John Cremona]

On 3 April 2015 at 09:07, Francois Bissey
<francoi...@canterbury.ac.nz> wrote:
> What does PKG_CONFIG_PATH says?

That is not set in my bash shell. Should I be looking elsewhere?

John

[John Cremona]

Also:

$ locate ft2build.h
/home/lmfdb/sage1/local/include/freetype2/ft2build.h
/home/lmfdb/sage2/local/include/freetype2/ft2build.h
/home/lmfdb/sage3/local/include/freetype2/ft2build.h
/usr/include/freetype2/ft2build.h

shows that the file ft2build.h is in all 3 of my sage build
directories as well as in a system place.

[Francois Bissey]

Well, you don’t seem to have one of these path ($SAGE_LOCAL/include)
as a -I parameter so something failed at detection time.
You have:
-I/home/lmfdb/sage2/local/include/libpng12
-I/home/lmfdb/sage/local/include/freetype2

Stuff like that happened before because the wrong path was somehow
taken from a previously installed version. Notice “sage” instead of
“sage2”.
I would have to dig the list to find what it was last time.

François

[John Cremona]

Thanks -- I am not sure it is worth while spending longer. One
difference between the two directories is that this one had an older
build from which I was starting; and it is also quite possible that
this directory is/was the one which I renamed when I decided that it
was necessary to have 3 instead of just one. (I need to build updated
versions of Sage while older versions are still running in
production).

I have done a make distclean; make and we'll see if that sorts it.

John

On 3 April 2015 at 09:26, Francois Bissey

[Emmanuel Charpentier]

FWIW, builds (with preemptive "make doc-clean") and passes all tests on a Corei7, 16GB Ram Debian (testing) machine.

HTH,
__
Emmanuel Charpentier

[Daniel Krenn]

Am 2015-04-02 um 03:35 schrieb Volker Braun:
> 819000f Updated Sage version to 6.6.rc2

git clone ...
make

does not work on Debian stable, see below.

Daniel

************************************************************************
Error installing package sagenb-0.11.4
************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file
/local/data/krenn/sage/6.6.rc2/logs/pkgs/sagenb-0.11.4.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/local/data/krenn/sage/6.6.rc2/local/var/tmp/sage/build/sagenb-0.11.4
and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd
'/local/data/krenn/sage/6.6.rc2/local/var/tmp/sage/build/sagenb-0.11.4'
&& '/local/data/krenn/sage/6.6.rc2/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************
make[2]: ***
[/local/data/krenn/sage/6.6.rc2/local/var/lib/sage/installed/sagenb-0.11.4]
Fehler 1
make[2]: Leaving directory `/local/data/krenn/sage/6.6.rc2/build'
make[1]: *** [all] Fehler 2
make[1]: Leaving directory `/local/data/krenn/sage/6.6.rc2/build'

real 117m6.926s
user 100m26.793s
sys 5m24.660s
***************************************************************
Error building Sage.

The following package(s) may have failed to build:

package: sagenb-0.11.4
log file: /local/data/krenn/sage/6.6.rc2/logs/pkgs/sagenb-0.11.4.log
build directory:
/local/data/krenn/sage/6.6.rc2/local/var/tmp/sage/build/sagenb-0.11.4

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.

make: *** [build] Fehler 1



/local/data/krenn/sage/6.6.rc2/logs/pkgs/sagenb-0.11.4.log:


Found local metadata for sagenb-0.11.4
Attempting to download package sagenb-0.11.4
>>> Trying to download
http://www.sagemath.org/packages/upstream/sagenb/sagenb-0.11.4.tar
[............................................................]
Checksum: 66593ecf18cbf77115279f6f1564854eb9b93df5 vs
66593ecf18cbf77115279f6f1564854eb9b93df5
sagenb-0.11.4
====================================================
Setting up build directory for sagenb-0.11.4
Finished set up
****************************************************
Host system:
Linux fmatbpc57 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
****************************************************
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--enable-gnu-unique-object --enable-plugin --enable-objc-gc
--with-arch-32=i586 --with-tune=generic --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)
****************************************************
Traceback (most recent call last):
File "/local/data/krenn/sage/6.6.rc2/local/bin/pip", line 9, in <module>
load_entry_point('pip==1.5.6', 'console_scripts', 'pip')()
File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line
521, in load_entry_point
File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line
2632, in load_entry_point
File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line
2312, in load
File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line
2318, in resolve
File
"/local/data/krenn/sage/6.6.rc2/local/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/__init__.py",
line 10, in <module>
from pip.util import get_installed_distributions, get_prog
File
"/local/data/krenn/sage/6.6.rc2/local/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/util.py",
line 18, in <module>
from pip._vendor.distlib import version
File
"/local/data/krenn/sage/6.6.rc2/local/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/_vendor/distlib/version.py",
line 14, in <module>
from .compat import string_types
File
"/local/data/krenn/sage/6.6.rc2/local/lib/python2.7/site-packages/pip-1.5.6-py2.7.egg/pip/_vendor/distlib/compat.py",
line 31, in <module>
from urllib2 import (Request, urlopen, URLError, HTTPError,
ImportError: cannot import name HTTPSHandler
Error: Installing SageNB failed.

[Volker Braun]

Apparently pip requires SSL... I take it you don't have a system-wide openssl(-devel) installation?

[kcrisman]

Apparently pip requires SSL... I take it you don't have a system-wide openssl(-devel) installation?

I was indeed wondering whether that change would make any problems. Also on older installations?  (Namely, which OS X versions should we assume will have this?  I honestly don't know.)

[Thierry]

Hi,

this is a known issue : pip requires that Python is built with ssl, but
openssl cannot be standard because of licensing, hence pip can only be
used to install optional packages, see
http://trac.sagemath.org/ticket/17368 for a discussion.

The following should work if you do not have libssl-dev on your system:

cd $SAGE_ROOT
./sage -i openssl
./sage -f python
make
./sage -pip install optional_package

Ciao,
Thierry

[Volker Braun]

I took a quick look at the pip sources and I think the ssl dependency can be stubbed out relatively easily. Did anybody try this? Really we should push this upstream, pip ought to be usable without ssl.

[Volker Braun]

I made http://trac.sagemath.org/ticket/18131 to deal with this

[Francois Bissey]

It depends. To just use pip as a local installer it probably will work
fine. If you want to connect to the pip repository to install extra
python packages you’ll need SSL (and a relatively recent one too).
The pip repo just won’t let you connect without SSL.

François

[Daniel Krenn]

-------- Weitergeleitete Nachricht --------
Betreff: Re: [sage-release] Sage 6.6.rc2 released
Datum: Tue, 07 Apr 2015 11:06:43 +0200
Von: Daniel Krenn <kr...@aon.at>
An: Samuel Lelièvre <samuel....@gmail.com>

Am 2015-04-05 um 14:03 schrieb Samuel Lelièvre:
> Try installing this Debian package before installing Sage:
>
> sudo apt-get install libssl-dev

So I cannot anymore build Sage without libssl-dev?

Daniel

[Volker Braun]

Yes, we want to install local tarballs.

[Francois Bissey]

I realise that;s what you want to do personally but I understand other use
pip to supplement sage’s collection of packages. William probably
wouldn’t be happy with a package manager that cannot pull packages.

Now, if we can just make sure that pip doesn’t need SSL for local install
but can still use it to pull packages that’s a win for everybody.

François

[Daniel Krenn]

http://trac.sagemath.org/ticket/18131

Am 2015-04-05 um 11:56 schrieb Daniel Krenn:

[Volker Braun]

Thats what I meant, provide stubs for when there is no ssl.

[Sébastien Labbé]

I get an error with libgd while compiling sage-6.6.rc2 on this machine:

$ uname -a

Darwin MacBookebastien.home 14.1.0 Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64 x86_64

Full libgd-2.1.0.p0.log is attached to this email. It finishes with:

mv -f .deps/gd2copypal.Tpo .deps/gd2copypal.Po

/bin/sh ../libtool --tag=CC   --mode=link gcc -std=gnu99  -g  -fvisibility=hidden -version-info 3:0:0 -no-undefined  -o libgd.la -rpath /Users/slabbe/Applications/sage-git/local/lib gd.lo gd_color.lo gd_color_map.lo gd_transform.lo gdfx.lo gd_security.lo gd_gd.lo gd_gd2.lo gd_io.lo gd_io_dp.lo gd_gif_in.lo gd_gif_out.lo gd_io_file.lo gd_io_ss.lo gd_jpeg.lo gd_png.lo gd_ss.lo gd_topal.lo gd_wbmp.lo gdcache.lo gdfontg.lo gdfontl.lo gdfontmb.lo gdfonts.lo gdfontt.lo gdft.lo gdhelpers.lo gdkanji.lo gdtables.lo gdxpm.lo wbmp.lo gd_filter.lo gd_nnquant.lo gd_rotate.lo gd_matrix.lo gd_interpolation.lo gd_crop.lo webpimg.lo gd_webp.lo gd_tiff.lo gd_tga.lo gd_bmp.lo gd_xbm.lo gd_color_match.lo -liconv -lz  -L/Users/slabbe/Applications/sage-git/local/lib -lpng12   -L/Users/slabbe/Applications/sage-git/local/lib -lfreetype -lz -lbz2 -lpng12

mv -f .deps/giftogd2.Tpo .deps/giftogd2.Po

grep: /Users/seb/Applications/sage/local/lib/libbz2.la: No such file or directory

sed: /Users/seb/Applications/sage/local/lib/libbz2.la: No such file or directory

libtool: link: `/Users/seb/Applications/sage/local/lib/libbz2.la' is not a valid libtool archive

make[2]: *** [libgd.la] Error 1

make[1]: *** [all] Error 2

make: *** [all-recursive] Error 1

Error building gd.

real 0m31.456s

user 0m20.854s

sys 0m12.668s

************************************************************************

Error installing package libgd-2.1.0.p0

************************************************************************

Please email sage-devel (http://groups.google.com/group/sage-devel)

explaining the problem and including the relevant part of the log file

  /Users/slabbe/Applications/sage-git/logs/pkgs/libgd-2.1.0.p0.log

Describe your computer, operating system, etc.

If you want to try to fix the problem yourself, *don't* just cd to

/Users/slabbe/Applications/sage-git/local/var/tmp/sage/build/libgd-2.1.0.p0 and type 'make' or whatever is appropriate.

Instead, the following commands setup all environment variables

correctly and load a subshell for you to debug the error:

  (cd '/Users/slabbe/Applications/sage-git/local/var/tmp/sage/build/libgd-2.1.0.p0' && '/Users/slabbe/Applications/sage-git/sage' --sh)

[Daniel Krenn]

Am 2015-04-05 um 13:24 schrieb Volker Braun:
> Apparently pip requires SSL... I take it you don't have a system-wide
> openssl(-devel) installation?

Is it possible to compile Sage with SSL from the beginning?

At the moment I (git-)clone Sage from trac in a new directory. Then type
make and only then I do "sage -i openssl && sage -f python && make".
This takes a very long time, since a lot is compiled twice. Is there an
option to do something like

WITH_OPENSSL=yes make

?

Best wishes

Daniel

[Volker Braun]

post the bzip2 install log

[Volker Braun]

OpenSSL is not GPL compatible, so we can't ship it.

[Vincent Delecroix]

On 08/04/2015, Volker Braun <vbrau...@gmail.com> wrote:
> OpenSSL is not GPL compatible, so we can't ship it.

But it does not prevent us to add an option such that 'sage -i
openssl' is executed *before* the compilation of Python.

[Volker Braun]

Yes it does.

[Vincent Delecroix]

At least, does 'sage -i openssl' before 'make' work?

On 08/04/2015, Volker Braun <vbrau...@gmail.com> wrote:
> Yes it does.
>
> On Wednesday, April 8, 2015 at 12:22:41 PM UTC+2, vdelecroix wrote:
>>

>> On 08/04/2015, Volker Braun <vbrau...@gmail.com <javascript:>> wrote:
>> > OpenSSL is not GPL compatible, so we can't ship it.
>>
>> But it does not prevent us to add an option such that 'sage -i
>> openssl' is executed *before* the compilation of Python.
>>
>

[John Cremona]

There is "make ssl" -- looking in the Makefile this does "make" and
then "./sage -i pyopenssl" which in view of this thread is not
sufficient?

John

[Daniel Krenn]

Am 2015-04-08 um 12:28 schrieb Vincent Delecroix:
> At least, does 'sage -i openssl' before 'make' work?

Seems to be possible (tried; but still compiling).

Daniel

[Vincent Delecroix]

If it does, it would be good to add it to the README and the relevant
section in the documentation.

Vincent

[John Cremona]

Item 10 in the README says this already:

10. OPTIONAL: Read this if you are intending to run a Sage notebook
server for multiple users. For security (i.e., to run
"notebook(secure=True)") you want to access the server using the
HTTPS protocol. First, install OpenSSL and the OpenSSL development
headers on your system if they are not already installed. Then
install pyOpenSSL by building Sage and then typing

./sage -i pyopenssl

Note that this command requires internet access. Alternatively,
"make ssl" builds Sage and installs pyOpenSSL.

John

> Vincent

[Sébastien Labbé]

On Wednesday, April 8, 2015 at 12:20:04 PM UTC+2, Volker Braun wrote:

post the bzip2 install log

The bzip2 install log is attached. It was successful finishing with:

....

real    0m16.313s

user    0m12.348s

sys     0m7.020s

Successfully installed bzip2-1.0.6.20140317

Deleting temporary build directory

/Users/seb/Applications/sage/local/var/tmp/sage/build/bzip2-1.0.6.20140317

Finished installing bzip2-1.0.6.20140317.spkg 

[Thierry]

Hi,

this is quite unrelated : pyopenssl is a wrapper to use openssl library
easily via python. Since it is not a standard package, i would suggest to
stop maintaining it (it is bitrotting and upgrading it will require to
maintain 4 additional dependencies) and let the user installing it with
pip if necessary (we did the same with sqlalchemy), see
http://trac.sagemath.org/ticket/17831

Here we are dealing with the issue that pip requires that python is built
with openssl, but openssl is not GPL-compatible, hence it can not be part
of the source tarball. So the user either have to install libssl-dev from
her distribution or run `sage -i openssl` before building python.

Ciao,
Thierry

[Sébastien Labbé]

On Wednesday, April 8, 2015 at 12:01:29 PM UTC+2, Sébastien Labbé wrote:

I get an error with libgd while compiling sage-6.6.rc2 on this machine:

Maybe I have an hypothesis for this error... I am currently reinstalling everything from scratch on my machine after I changed the hard disk and memory card. I am realizing now that I changed the username of my account during the compilation (running make the first time broke because the command line tools were missing). So it may explain why there is a problem finding bzip2 when running make again which was compiled earlier...

Let me recompile from scratch... I will give an update afterwards.

Sebastien

[Volker Braun]

bzip2 installed /Users/seb/Applications/sage/local/lib/libbz2.la, but it seems to be gone now. Who deleted it?

[John Cremona]

On 8 April 2015 at 12:26, Thierry <sage-goo...@lma.metelu.net> wrote:
> Hi,
>
> this is quite unrelated : pyopenssl is a wrapper to use openssl library
> easily via python. Since it is not a standard package, i would suggest to
> stop maintaining it (it is bitrotting and upgrading it will require to
> maintain 4 additional dependencies) and let the user installing it with
> pip if necessary (we did the same with sqlalchemy), see
> http://trac.sagemath.org/ticket/17831
>
> Here we are dealing with the issue that pip requires that python is built
> with openssl, but openssl is not GPL-compatible, hence it can not be part
> of the source tarball. So the user either have to install libssl-dev from
> her distribution or run `sage -i openssl` before building python.

Thanks for clarifying. I always mix up the pkgs openssl and
pyopenssl, so I should have kept quiet.

John

[Sébastien Labbé]

On Wednesday, April 8, 2015 at 1:35:04 PM UTC+2, Volker Braun wrote:

bzip2 installed /Users/seb/Applications/sage/local/lib/libbz2.la, but it seems to be gone now. Who deleted it?

Nobody, it is still there. Thanks for the follow up. I now understand what is happening. Not only I changed my user account, but I also moved the sage tree after the first incomplete compilation. This is why the libbz2.la can't be found while running make the second time. Recompiling from scratch should fix this. Sorry for the noise.

Sébastien

[leif]

It used to work and hence still *should*. In fact, we explicitly added
support for downloading and installing optional packages /before/
building Sage a while ago to avoid unnecessary recompilation, especially
of Python because of the SSL issue.


Nevertheless, I'd recommend to install the distro's version of
libssl-dev (package name of OpenSSL on Debian) system-wide whenever
possible; there've been dozens of security updates for OpenSSL in the
last few month, and the optional Sage package isn't updated that
frequently nor fast (not to mention you don't get a reminder even if it is).

I recall at some point William even deleted the "current" optional
package because it was outdated and lacked important security fixes.


-leif

[William Stein]

On Wed, Apr 8, 2015 at 7:26 AM, leif <not.r...@online.de> wrote:
> On 04/08/2015 12:48 PM, Daniel Krenn wrote:
>> Am 2015-04-08 um 12:28 schrieb Vincent Delecroix:
>>> At least, does 'sage -i openssl' before 'make' work?
>>
>> Seems to be possible (tried; but still compiling).
>
> It used to work and hence still *should*. In fact, we explicitly added
> support for downloading and installing optional packages /before/
> building Sage a while ago to avoid unnecessary recompilation, especially
> of Python because of the SSL issue.
>
>
> Nevertheless, I'd recommend to install the distro's version of
> libssl-dev (package name of OpenSSL on Debian) system-wide whenever
> possible; there've been dozens of security updates for OpenSSL in the
> last few month, and the optional Sage package isn't updated that
> frequently nor fast (not to mention you don't get a reminder even if it is).

Huge +1 to this!

-- William

> I recall at some point William even deleted the "current" optional
> package because it was outdated and lacked important security fixes.



>
>
> -leif
>

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

--
William (http://wstein.org)

[Vincent Delecroix]

On 08/04/2015, leif <not.r...@online.de> wrote:
> On 04/08/2015 12:48 PM, Daniel Krenn wrote:
>> Am 2015-04-08 um 12:28 schrieb Vincent Delecroix:
>>> At least, does 'sage -i openssl' before 'make' work?
>>
>> Seems to be possible (tried; but still compiling).
>
> It used to work and hence still *should*. In fact, we explicitly added
> support for downloading and installing optional packages /before/
> building Sage a while ago to avoid unnecessary recompilation, especially
> of Python because of the SSL issue.
>
>
> Nevertheless, I'd recommend to install the distro's version of
> libssl-dev (package name of OpenSSL on Debian) system-wide whenever
> possible; there've been dozens of security updates for OpenSSL in the
> last few month, and the optional Sage package isn't updated that
> frequently nor fast (not to mention you don't get a reminder even if it
> is).

Some people take care of it

# 18079 Update openssl to 1.0.2a (closed 5 days ago)
# 17691 Update openssl to 1.0.2 (closed 2 months ago)
# 17132 Update openssl to 1.0.1j (closed 5 months ago)
# 16454 Update openssl to 1.0.1h (closed 9 months ago)

But of course, I would recommend a system wide installation since Sage
does not have the manpower of a OS distribution.

Vincent

[kcrisman]

Unrelated to ssl, presumably related to in-place Cythonizing:

$ git commit

...

# Untracked files:

#   (use "git add <file>..." to include in what will be committed)

#

# src/sage/algebras/letterplace/free_algebra_element_letterplace.cpp

# src/sage/algebras/letterplace/free_algebra_letterplace.cpp

# src/sage/algebras/letterplace/letterplace_ideal.cpp

# src/sage/algebras/quatalg/quaternion_algebra_cython.cpp

# src/sage/algebras/quatalg/quaternion_algebra_element.cpp

It would be nice for those to go away.

[leif]

From the rc1 thread:


On 03/30/2015 03:15 PM, Jeroen Demeyer wrote:
> On 2015-03-30 10:28, Simon King wrote:
>> But how did they come there? I thought that meanwhile there is a
>> separate folder for compiling Sage code.
> Those files still date from the time when there wasn't a separate
> folder. You can safely delete them.



On 03/30/2015 10:37 AM, Volker Braun wrote:
> On Monday, March 30, 2015 at 10:29:14 AM UTC+2, Simon King wrote:
>
> On 2015-03-30, Volker Braun <vbrau...@gmail.com <javascript:>> wrote:
> > You can delete the extraneous files.
> OK. But how did they come there? I thought that meanwhile there is a
> separate folder for compiling Sage code.
>
>
> They were in the .gitignore before but the ticket that moved them also
> remove the ignore entries for the old file locations.



-leif

[kcrisman]

From the rc1 thread:


On 03/30/2015 03:15 PM, Jeroen Demeyer wrote:
> On 2015-03-30 10:28, Simon King wrote:
>> But how did they come there? I thought that meanwhile there is a
>> separate folder for compiling Sage code.
> Those files still date from the time when there wasn't a separate
> folder. You can safely delete them.

Ok.  Followup:

# src/sage/tests/cython.c

# src/sage/tests/interrupt.c

# src/sage/tests/stl_vector.cpp

$ ls -r src/sage/tests/*.c

src/sage/tests/interrupt.c src/sage/tests/c_lib.c

src/sage/tests/cython.c

$ ls -r src/sage/tests/*.cpp

src/sage/tests/stl_vector.cpp

Apparently there is an extra .c file that isn't in the git list.  I'm hesitant to remove ALL .c, .h, and .cpp files unless I'm sure they are all unneeded... but I don't see how to identify the ones that aren't in that list.

[Volker Braun]

You can always delete everything that is not under version control. Thats the point of it. Run "git clean -f" to do it automatically.

[Sébastien Labbé]

Let me recompile from scratch... I will give an update afterwards.

Testing that Sage starts...

[2015-04-09 19:47:34] Sage version 6.6.rc2, released 2015-04-02

Yes, Sage starts.

Sébastien

[kcrisman]

 

Apparently there is an extra .c file that isn't in the git list.  I'm hesitant to remove ALL .c, .h, and .cpp files unless I'm sure they are all unneeded... but I don't see how to identify the ones that aren't in that list.

You can always delete everything that is not under version control. Thats the point of it. Run "git clean -f" to do it automatically.

 

Sure, I just didn't know how to do it without removing some that *were* under control, or writing some shell script.  Thanks, that command is very helpful!