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
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
You can always delete everything that is not under version control. Thats
the point of it. Run git clean -f to do it automatically.
On Thursday, April 9, 2015 at 5:25:01 PM UTC+2, kcrisman wrote:
From the rc1 thread:
On 03/30/2015 03:15 PM, Jeroen Demeyer wrote:
On 2015-03-30 10:28,
On 8 April 2015 at 11:53, Vincent Delecroix 20100.delecr...@gmail.com wrote:
On 08/04/2015, Daniel Krenn kr...@aon.at 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).
If it does,
On 8 April 2015 at 12:26, Thierry sage-googlesu...@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
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
At least, does 'sage -i openssl' before 'make' work?
On 08/04/2015, Volker Braun vbraun.n...@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
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
OpenSSL is not GPL compatible, so we can't ship it.
On Wednesday, April 8, 2015 at 12:12:05 PM UTC+2, Daniel Krenn wrote:
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
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
#
On 08/04/2015, leif not.rea...@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
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
On Wed, Apr 8, 2015 at 7:26 AM, leif not.rea...@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
On 04/08/2015 07:26 PM, kcrisman wrote:
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
14 matches
Mail list logo
