[sage-devel] Re: Building 9.0 on macOS: test suite failure with cython-0.29.12.p0 and nose-1.3.7

2020-01-11 Thread Szabolcs Horvát 
Thanks for confirming it's not just me. It looks like out of those 6 
failures only 2 remain then.

On Saturday, 11 January 2020 19:27:21 UTC+1, John H Palmieri wrote:
>
> It is safe to build without setting SAGE_CHECK. Also, some packages are 
> known to fail their test suites — see 
> https://groups.google.com/d/msg/sage-devel/abysgIIVGZI/fF7efL9RAwAJ, for 
> example.
>
>
>
> On Saturday, January 11, 2020 at 2:40:04 AM UTC-8, Szabolcs Horvát wrote:
>>
>> Hello everyone,
>>
>> I tried to build Sage from source on macOS 10.14.6 / Xcode 11.3. Some 
>> functionality, such as using CBC for integer programming problems, is only 
>> supported if Sage is built from source.
>>
>> I set SAGE_CHECK="yes". Some of the tests seem to fail.
>>
>> I was wondering if others have managed to build Sage from source on this 
>> platform and if the test suite passes for you.
>>
>> I cannot think of anything on my system that could have interfered with 
>> the build. I do not have Homebrew. I have MacPorts and Anaconda Python, but 
>> I removed both from the PATH environment variable before starting the build 
>> (reverted PATH to a pristine value). 
>>
>> I have attached the log files as instructed.
>>
>>
>> For cython, several tests appear to fail because of overflow errors with 
>> long long. For example,
>>
>> Failed example:
>> long_long_abs(-max_long_long-1) #doctest: +ELLIPSIS
>> Expected:
>> Traceback (most recent call last):
>> ...
>> OverflowError: ...
>> Got:
>> -9223372036854775808
>>
>>
>> For nose, the log file suggests that the tests are missing or not copied 
>> to the final location?
>>
>> ValueError: Working directory 'build/tests' not found, or not a directory
>> Error running functional_tests.
>>
>> I could just not set SAGE_CHECK="yes" but is that safe?
>>
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/433acbba-bac1-4826-84db-402a4af9591e%40googlegroups.com.

[sage-devel] Re: Building 9.0 on macOS: test suite failure with cython-0.29.12.p0 and nose-1.3.7

2020-01-11 Thread John H Palmieri 
It is safe to build without setting SAGE_CHECK. Also, some packages are 
known to fail their test suites — see 
https://groups.google.com/d/msg/sage-devel/abysgIIVGZI/fF7efL9RAwAJ, for 
example.



On Saturday, January 11, 2020 at 2:40:04 AM UTC-8, Szabolcs Horvát wrote:
>
> Hello everyone,
>
> I tried to build Sage from source on macOS 10.14.6 / Xcode 11.3. Some 
> functionality, such as using CBC for integer programming problems, is only 
> supported if Sage is built from source.
>
> I set SAGE_CHECK="yes". Some of the tests seem to fail.
>
> I was wondering if others have managed to build Sage from source on this 
> platform and if the test suite passes for you.
>
> I cannot think of anything on my system that could have interfered with 
> the build. I do not have Homebrew. I have MacPorts and Anaconda Python, but 
> I removed both from the PATH environment variable before starting the build 
> (reverted PATH to a pristine value). 
>
> I have attached the log files as instructed.
>
>
> For cython, several tests appear to fail because of overflow errors with 
> long long. For example,
>
> Failed example:
> long_long_abs(-max_long_long-1) #doctest: +ELLIPSIS
> Expected:
> Traceback (most recent call last):
> ...
> OverflowError: ...
> Got:
> -9223372036854775808
>
>
> For nose, the log file suggests that the tests are missing or not copied 
> to the final location?
>
> ValueError: Working directory 'build/tests' not found, or not a directory
> Error running functional_tests.
>
> I could just not set SAGE_CHECK="yes" but is that safe?
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/95a5f5e1-d0da-48e4-97c4-df240780acd1%40googlegroups.com.

[sage-devel] Re: Build of 9.0 failed at R

2020-01-11 Thread Frédéric Chapoton 
If you repeat "make build -j4" until this is the only failure, this does 
not prevent sage to work.

So if you do not need R, you can ignore that.

I have the same problem on several machine with Ubuntu 19.10

F

Le samedi 11 janvier 2020 16:18:37 UTC+1, Malcolm MacCallum a écrit :
>
> I am using a Dell Inspiron 13, 5000 series, running
> Ubuntu Linux 18.01.
>
> The error in building R as seen in the attached log
> led to the overall build failing. I would have liked
> to have an updated sage having just changed Linux
> distro to Ubuntu. Advice on how to fix this welcomed!
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ac7a9100-4255-4dc0-993d-9221fd39ace4%40googlegroups.com.

[sage-devel] Re: Building 9.0 on macOS: test suite failure with cython-0.29.12.p0 and nose-1.3.7

2020-01-11 Thread Matthias Koeppe 
On Saturday, January 11, 2020 at 5:40:04 AM UTC-5, Szabolcs Horvát wrote:
>
> I tried to build Sage from source on macOS 10.14.6 / Xcode 11.3. Some 
> functionality, such as using CBC for integer programming problems, is only 
> supported if Sage is built from source.
>
>
Note that there is now 
https://github.com/mkoeppe/sage-numerical-backends-coin, which you can 
install on top of binary distributions of sage.
 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8b5358ea-9506-4147-b5cd-34a561e44561%40googlegroups.com.

Re: [sage-devel] 9.1.beta0: issue with sage-numerical-backends-gurobi

2020-01-11 Thread Matthias Koeppe 
Fixed in 
https://github.com/mkoeppe/sage-numerical-backends-gurobi/commit/b756bf8b01be1a3a3f8ee2b0493687bd986db0f5

I'll make a new release soon.

On Saturday, January 11, 2020 at 5:26:48 AM UTC-5, David Coudert wrote:
>
> Done. This is now issue #1
>
> Le samedi 11 janvier 2020 11:19:23 UTC+1, Dima Pasechnik a écrit :
>>
>>
>>
>> On Sat, 11 Jan 2020, 10:14 David Coudert,  wrote:
>>
>>> I have an error when trying to install the gurobi backend that is now a 
>>> separate optional package.
>>> I followed the instructions for installing the gurobi backend with sage 
>>> 9.1.beta0 and macOS Mojave 10.14.6.
>>> I have gurobi 8.11 and gurobi.sh is in my path (so no need to set 
>>> GUROBI_HOME).
>>> (note that I successfully installed the cplex backend).
>>>
>>> Should I report this issue directly on 
>>> https://github.com/mkoeppe/sage-numerical-backends-gurobi ?
>>>
>>
>> it would help if you copied this report there too.
>>
>>>
>>> confetti:sage dcoudert$ ./sage -python -m pip install 
>>> sage-numerical-backends-gurobi
>>>
>>> Collecting sage-numerical-backends-gurobi
>>>
>>>   Downloading 
>>> https://files.pythonhosted.org/packages/2c/5c/e1532bb6cde28cf86ebffd408ccb500d7b846bc29bbd1c5e479a2f18acb6/sage_numerical_backends_gurobi-9.0b12.tar.gz
>>>
>>> Requirement already satisfied: sphinx in 
>>> ./local/lib/python3.7/site-packages (from sage-numerical-backends-gurobi) 
>>> (1.8.5)
>>>
>>> Requirement already satisfied: six>=1.5 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (1.12.0)
>>>
>>> Requirement already satisfied: Jinja2>=2.3 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (2.10)
>>>
>>> Requirement already satisfied: Pygments>=2.0 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (2.3.1)
>>>
>>> Requirement already satisfied: docutils>=0.11 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (0.14)
>>>
>>> Requirement already satisfied: snowballstemmer>=1.1 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (1.2.1)
>>>
>>> Requirement already satisfied: babel!=2.0,>=1.3 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (2.6.0)
>>>
>>> Requirement already satisfied: alabaster<0.8,>=0.7 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (0.7.12)
>>>
>>> Requirement already satisfied: imagesize in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (1.1.0)
>>>
>>> Requirement already satisfied: requests>=2.0.0 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (2.13.0)
>>>
>>> Requirement already satisfied: setuptools in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (40.6.3)
>>>
>>> Requirement already satisfied: packaging in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (18.0)
>>>
>>> Requirement already satisfied: sphinxcontrib-websupport in 
>>> ./local/lib/python3.7/site-packages (from 
>>> sphinx->sage-numerical-backends-gurobi) (1.1.0)
>>>
>>> Requirement already satisfied: MarkupSafe>=0.23 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> Jinja2>=2.3->sphinx->sage-numerical-backends-gurobi) (1.1.0)
>>>
>>> Requirement already satisfied: pytz>=0a in 
>>> ./local/lib/python3.7/site-packages (from 
>>> babel!=2.0,>=1.3->sphinx->sage-numerical-backends-gurobi) (2018.7)
>>>
>>> Requirement already satisfied: pyparsing>=2.0.2 in 
>>> ./local/lib/python3.7/site-packages (from 
>>> packaging->sphinx->sage-numerical-backends-gurobi) (2.3.0)
>>>
>>> Installing collected packages: sage-numerical-backends-gurobi
>>>
>>>   Running setup.py install for sage-numerical-backends-gurobi ... error
>>>
>>> Complete output from command /Users/dcoudert/sage/local/bin/python3 
>>> -u -c "import setuptools, 
>>> tokenize;__file__='/private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-install-t4k429rc/sage-numerical-backends-gurobi/setup.py';f=getattr(tokenize,
>>>  
>>> 'open', open)(__file__);code=f.read().replace('\r\n', 
>>> '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record 
>>> /private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-record-sk9om1cp/install-record.txt
>>>  
>>> --single-version-externally-managed --compile:
>>>
>>> Using GUROBI_HOME obtained from gurobi.sh:
>>>
>>> GUROBI_HOME is not set, or it does not point to a directory with a 
>>> Gurobi installation.  Trying to link against -lgurobi
>>>
>>> Checking whether HAVE_SAGE_CPYTHON_STRING...
>>>
>>> Checking whether HAVE_ADD_COL_UNTYPED_ARGS...
>>>
>>> Using compile_time_env: {'HAVE_SAGE_CPYTHON_STRING': True, 
>>> 'HAVE_ADD_COL_UNTYPED_ARGS': True}
>>>
>>> running install
>>>
>>> running build
>

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread arojas 
El sábado, 11 de enero de 2020, 11:23:32 (UTC+1), Dima Pasechnik escribió:
>
>
>
> On Sat, 11 Jan 2020, 10:19 arojas, > wrote:
>
>> I suspect this may be due to our openblas package only providing 
>> libblas.so (not libcblas.so or liblapack.so, which in our case come from 
>> the netlib blas).
>>
>
> Are you saying that your libopenblas.so does not provide everything that 
> is in openblas by default? 
>
> This is largely defeating its purpose.
> Sage's openblas does provide the cblas and lapack capabilities.
>

 In that case, openblas' spkg-configure should check whether cblas symbols 
are provided by the system openblas, and if not it should compile sage's 
one. It shouldn't unconditionally assume that that's always the case.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a1516e56-ab25-410e-be0f-75a7a6713466%40googlegroups.com.

Re: [sage-devel] 9.1.beta0: issue with sage-numerical-backends-gurobi

2020-01-11 Thread David Coudert 
Done. This is now issue #1

Le samedi 11 janvier 2020 11:19:23 UTC+1, Dima Pasechnik a écrit :
>
>
>
> On Sat, 11 Jan 2020, 10:14 David Coudert,  > wrote:
>
>> I have an error when trying to install the gurobi backend that is now a 
>> separate optional package.
>> I followed the instructions for installing the gurobi backend with sage 
>> 9.1.beta0 and macOS Mojave 10.14.6.
>> I have gurobi 8.11 and gurobi.sh is in my path (so no need to set 
>> GUROBI_HOME).
>> (note that I successfully installed the cplex backend).
>>
>> Should I report this issue directly on 
>> https://github.com/mkoeppe/sage-numerical-backends-gurobi ?
>>
>
> it would help if you copied this report there too.
>
>>
>> confetti:sage dcoudert$ ./sage -python -m pip install 
>> sage-numerical-backends-gurobi
>>
>> Collecting sage-numerical-backends-gurobi
>>
>>   Downloading 
>> https://files.pythonhosted.org/packages/2c/5c/e1532bb6cde28cf86ebffd408ccb500d7b846bc29bbd1c5e479a2f18acb6/sage_numerical_backends_gurobi-9.0b12.tar.gz
>>
>> Requirement already satisfied: sphinx in 
>> ./local/lib/python3.7/site-packages (from sage-numerical-backends-gurobi) 
>> (1.8.5)
>>
>> Requirement already satisfied: six>=1.5 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (1.12.0)
>>
>> Requirement already satisfied: Jinja2>=2.3 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (2.10)
>>
>> Requirement already satisfied: Pygments>=2.0 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (2.3.1)
>>
>> Requirement already satisfied: docutils>=0.11 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (0.14)
>>
>> Requirement already satisfied: snowballstemmer>=1.1 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (1.2.1)
>>
>> Requirement already satisfied: babel!=2.0,>=1.3 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (2.6.0)
>>
>> Requirement already satisfied: alabaster<0.8,>=0.7 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (0.7.12)
>>
>> Requirement already satisfied: imagesize in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (1.1.0)
>>
>> Requirement already satisfied: requests>=2.0.0 in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (2.13.0)
>>
>> Requirement already satisfied: setuptools in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (40.6.3)
>>
>> Requirement already satisfied: packaging in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (18.0)
>>
>> Requirement already satisfied: sphinxcontrib-websupport in 
>> ./local/lib/python3.7/site-packages (from 
>> sphinx->sage-numerical-backends-gurobi) (1.1.0)
>>
>> Requirement already satisfied: MarkupSafe>=0.23 in 
>> ./local/lib/python3.7/site-packages (from 
>> Jinja2>=2.3->sphinx->sage-numerical-backends-gurobi) (1.1.0)
>>
>> Requirement already satisfied: pytz>=0a in 
>> ./local/lib/python3.7/site-packages (from 
>> babel!=2.0,>=1.3->sphinx->sage-numerical-backends-gurobi) (2018.7)
>>
>> Requirement already satisfied: pyparsing>=2.0.2 in 
>> ./local/lib/python3.7/site-packages (from 
>> packaging->sphinx->sage-numerical-backends-gurobi) (2.3.0)
>>
>> Installing collected packages: sage-numerical-backends-gurobi
>>
>>   Running setup.py install for sage-numerical-backends-gurobi ... error
>>
>> Complete output from command /Users/dcoudert/sage/local/bin/python3 
>> -u -c "import setuptools, 
>> tokenize;__file__='/private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-install-t4k429rc/sage-numerical-backends-gurobi/setup.py';f=getattr(tokenize,
>>  
>> 'open', open)(__file__);code=f.read().replace('\r\n', 
>> '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record 
>> /private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-record-sk9om1cp/install-record.txt
>>  
>> --single-version-externally-managed --compile:
>>
>> Using GUROBI_HOME obtained from gurobi.sh:
>>
>> GUROBI_HOME is not set, or it does not point to a directory with a 
>> Gurobi installation.  Trying to link against -lgurobi
>>
>> Checking whether HAVE_SAGE_CPYTHON_STRING...
>>
>> Checking whether HAVE_ADD_COL_UNTYPED_ARGS...
>>
>> Using compile_time_env: {'HAVE_SAGE_CPYTHON_STRING': True, 
>> 'HAVE_ADD_COL_UNTYPED_ARGS': True}
>>
>> running install
>>
>> running build
>>
>> running build_py
>>
>> creating build
>>
>> creating build/lib.macosx-10.9-x86_64-3.7
>>
>> creating 
>> build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi
>>
>> copying sage_numerical_backends_gurobi/__init__.py -> 
>> build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi
>>
>> copying sage_n

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread Dima Pasechnik 
On Sat, 11 Jan 2020, 10:19 arojas,  wrote:

> I suspect this may be due to our openblas package only providing
> libblas.so (not libcblas.so or liblapack.so, which in our case come from
> the netlib blas).
>

Are you saying that your libopenblas.so does not provide everything that is
in openblas by default?

This is largely defeating its purpose.
Sage's openblas does provide the cblas and lapack capabilities.



> El sábado, 11 de enero de 2020, 10:38:07 (UTC+1), Dima Pasechnik escribió:
>>
>>
>>
>> On Sat, 11 Jan 2020, 09:21 Antonio Rojas,  wrote:
>>
>>> openblas is not being built in Sage, the system one is detected and used
>>> after FS#27870. FWIW, building our distro fflas-ffpack package with our
>>> system openblas works fine.
>>>
>>
>> the question is why on your system it causes a problem. this setup, with
>> external openblas, has been tested on many different OS.
>>
>>
>>> El sábado, 11 de enero de 2020, 10:00:43 (UTC+1), Dima Pasechnik
>>> escribió:

 On Sat, Jan 11, 2020 at 8:57 AM Antonio Rojas 
 wrote:
 >
 > I don't think so - I'm pretty sure I've built it successfully after
 that commit.
 >
 please compare the system openblas linkage with the one you build in
 Sage, and post the outputs of ldd here.
 I am pretty sure there is an interesting
 difference, I only don't know which way.


 > El sábado, 11 de enero de 2020, 9:25:04 (UTC+1), Dima Pasechnik
 escribió:
 >>
 >> isn't it due to https://trac.sagemath.org/ticket/27444 - which
 removed
 >> --disable-openmp from fflas-ffpack flags ?
 >> see https://trac.sagemath.org/ticket/27444#comment:34
 >>
 >> On Sat, Jan 11, 2020 at 7:53 AM Antonio Rojas 
 wrote:
 >> >
 >> > Build fails at fflas-ffpack, log attached. Seems related to
 FS#27870
 >> >
 >> > --
 >> > 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-...@googlegroups.com.
 >> > To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/9768e0af-b10a-4721-844c-6a81832a117b%40googlegroups.com.

 >
 > --
 > 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-...@googlegroups.com.
 > To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/488d598b-5232-4ee5-90ef-82b3ebd982fd%40googlegroups.com.


>>> --
>>> 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-...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/16b2c949-712d-4c2e-9833-621da436cbb9%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/159ed5d5-a263-41e7-89fa-da16e4450a40%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3HMaPGJdMwuaoENJ4Z%3DyMTCPv6pVK8hY36FfrQJNdgYA%40mail.gmail.com.

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread arojas 
I suspect this may be due to our openblas package only providing libblas.so 
(not libcblas.so or liblapack.so, which in our case come from the netlib 
blas).

El sábado, 11 de enero de 2020, 10:38:07 (UTC+1), Dima Pasechnik escribió:
>
>
>
> On Sat, 11 Jan 2020, 09:21 Antonio Rojas, > 
> wrote:
>
>> openblas is not being built in Sage, the system one is detected and used 
>> after FS#27870. FWIW, building our distro fflas-ffpack package with our 
>> system openblas works fine.
>>
>
> the question is why on your system it causes a problem. this setup, with 
> external openblas, has been tested on many different OS.
>
>
>> El sábado, 11 de enero de 2020, 10:00:43 (UTC+1), Dima Pasechnik escribió:
>>>
>>> On Sat, Jan 11, 2020 at 8:57 AM Antonio Rojas  wrote: 
>>> > 
>>> > I don't think so - I'm pretty sure I've built it successfully after 
>>> that commit. 
>>> > 
>>> please compare the system openblas linkage with the one you build in 
>>> Sage, and post the outputs of ldd here. 
>>> I am pretty sure there is an interesting 
>>> difference, I only don't know which way. 
>>>
>>>
>>> > El sábado, 11 de enero de 2020, 9:25:04 (UTC+1), Dima Pasechnik 
>>> escribió: 
>>> >> 
>>> >> isn't it due to https://trac.sagemath.org/ticket/27444 - which 
>>> removed 
>>> >> --disable-openmp from fflas-ffpack flags ? 
>>> >> see https://trac.sagemath.org/ticket/27444#comment:34 
>>> >> 
>>> >> On Sat, Jan 11, 2020 at 7:53 AM Antonio Rojas  
>>> wrote: 
>>> >> > 
>>> >> > Build fails at fflas-ffpack, log attached. Seems related to 
>>> FS#27870 
>>> >> > 
>>> >> > -- 
>>> >> > 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-...@googlegroups.com. 
>>> >> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/9768e0af-b10a-4721-844c-6a81832a117b%40googlegroups.com.
>>>  
>>>
>>> > 
>>> > -- 
>>> > 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-...@googlegroups.com. 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/488d598b-5232-4ee5-90ef-82b3ebd982fd%40googlegroups.com.
>>>  
>>>
>>>
>> -- 
>> 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-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/16b2c949-712d-4c2e-9833-621da436cbb9%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/159ed5d5-a263-41e7-89fa-da16e4450a40%40googlegroups.com.

Re: [sage-devel] 9.1.beta0: issue with sage-numerical-backends-gurobi

2020-01-11 Thread Dima Pasechnik 
On Sat, 11 Jan 2020, 10:14 David Coudert,  wrote:

> I have an error when trying to install the gurobi backend that is now a
> separate optional package.
> I followed the instructions for installing the gurobi backend with sage
> 9.1.beta0 and macOS Mojave 10.14.6.
> I have gurobi 8.11 and gurobi.sh is in my path (so no need to set
> GUROBI_HOME).
> (note that I successfully installed the cplex backend).
>
> Should I report this issue directly on
> https://github.com/mkoeppe/sage-numerical-backends-gurobi ?
>

it would help if you copied this report there too.

>
> confetti:sage dcoudert$ ./sage -python -m pip install
> sage-numerical-backends-gurobi
>
> Collecting sage-numerical-backends-gurobi
>
>   Downloading
> https://files.pythonhosted.org/packages/2c/5c/e1532bb6cde28cf86ebffd408ccb500d7b846bc29bbd1c5e479a2f18acb6/sage_numerical_backends_gurobi-9.0b12.tar.gz
>
> Requirement already satisfied: sphinx in
> ./local/lib/python3.7/site-packages (from sage-numerical-backends-gurobi)
> (1.8.5)
>
> Requirement already satisfied: six>=1.5 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (1.12.0)
>
> Requirement already satisfied: Jinja2>=2.3 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (2.10)
>
> Requirement already satisfied: Pygments>=2.0 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (2.3.1)
>
> Requirement already satisfied: docutils>=0.11 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (0.14)
>
> Requirement already satisfied: snowballstemmer>=1.1 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (1.2.1)
>
> Requirement already satisfied: babel!=2.0,>=1.3 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (2.6.0)
>
> Requirement already satisfied: alabaster<0.8,>=0.7 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (0.7.12)
>
> Requirement already satisfied: imagesize in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (1.1.0)
>
> Requirement already satisfied: requests>=2.0.0 in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (2.13.0)
>
> Requirement already satisfied: setuptools in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (40.6.3)
>
> Requirement already satisfied: packaging in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (18.0)
>
> Requirement already satisfied: sphinxcontrib-websupport in
> ./local/lib/python3.7/site-packages (from
> sphinx->sage-numerical-backends-gurobi) (1.1.0)
>
> Requirement already satisfied: MarkupSafe>=0.23 in
> ./local/lib/python3.7/site-packages (from
> Jinja2>=2.3->sphinx->sage-numerical-backends-gurobi) (1.1.0)
>
> Requirement already satisfied: pytz>=0a in
> ./local/lib/python3.7/site-packages (from
> babel!=2.0,>=1.3->sphinx->sage-numerical-backends-gurobi) (2018.7)
>
> Requirement already satisfied: pyparsing>=2.0.2 in
> ./local/lib/python3.7/site-packages (from
> packaging->sphinx->sage-numerical-backends-gurobi) (2.3.0)
>
> Installing collected packages: sage-numerical-backends-gurobi
>
>   Running setup.py install for sage-numerical-backends-gurobi ... error
>
> Complete output from command /Users/dcoudert/sage/local/bin/python3 -u
> -c "import setuptools,
> tokenize;__file__='/private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-install-t4k429rc/sage-numerical-backends-gurobi/setup.py';f=getattr(tokenize,
> 'open', open)(__file__);code=f.read().replace('\r\n',
> '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record
> /private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-record-sk9om1cp/install-record.txt
> --single-version-externally-managed --compile:
>
> Using GUROBI_HOME obtained from gurobi.sh:
>
> GUROBI_HOME is not set, or it does not point to a directory with a
> Gurobi installation.  Trying to link against -lgurobi
>
> Checking whether HAVE_SAGE_CPYTHON_STRING...
>
> Checking whether HAVE_ADD_COL_UNTYPED_ARGS...
>
> Using compile_time_env: {'HAVE_SAGE_CPYTHON_STRING': True,
> 'HAVE_ADD_COL_UNTYPED_ARGS': True}
>
> running install
>
> running build
>
> running build_py
>
> creating build
>
> creating build/lib.macosx-10.9-x86_64-3.7
>
> creating
> build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi
>
> copying sage_numerical_backends_gurobi/__init__.py ->
> build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi
>
> copying sage_numerical_backends_gurobi/gurobi_backend.pxd ->
> build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi
>
> running build_ext
>
> building 'sage_numerical_backends_gurobi.gurobi_backend' extension
>
> creating build/temp.macosx-10.9-x86_64-3.7
>
> creating
> build/t

[sage-devel] 9.1.beta0: issue with sage-numerical-backends-gurobi

2020-01-11 Thread David Coudert 
I have an error when trying to install the gurobi backend that is now a 
separate optional package.
I followed the instructions for installing the gurobi backend with sage 
9.1.beta0 and macOS Mojave 10.14.6.
I have gurobi 8.11 and gurobi.sh is in my path (so no need to set 
GUROBI_HOME).
(note that I successfully installed the cplex backend).

Should I report this issue directly 
on https://github.com/mkoeppe/sage-numerical-backends-gurobi ?

confetti:sage dcoudert$ ./sage -python -m pip install 
sage-numerical-backends-gurobi

Collecting sage-numerical-backends-gurobi

  Downloading 
https://files.pythonhosted.org/packages/2c/5c/e1532bb6cde28cf86ebffd408ccb500d7b846bc29bbd1c5e479a2f18acb6/sage_numerical_backends_gurobi-9.0b12.tar.gz

Requirement already satisfied: sphinx in 
./local/lib/python3.7/site-packages (from sage-numerical-backends-gurobi) 
(1.8.5)

Requirement already satisfied: six>=1.5 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (1.12.0)

Requirement already satisfied: Jinja2>=2.3 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (2.10)

Requirement already satisfied: Pygments>=2.0 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (2.3.1)

Requirement already satisfied: docutils>=0.11 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (0.14)

Requirement already satisfied: snowballstemmer>=1.1 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (1.2.1)

Requirement already satisfied: babel!=2.0,>=1.3 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (2.6.0)

Requirement already satisfied: alabaster<0.8,>=0.7 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (0.7.12)

Requirement already satisfied: imagesize in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (1.1.0)

Requirement already satisfied: requests>=2.0.0 in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (2.13.0)

Requirement already satisfied: setuptools in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (40.6.3)

Requirement already satisfied: packaging in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (18.0)

Requirement already satisfied: sphinxcontrib-websupport in 
./local/lib/python3.7/site-packages (from 
sphinx->sage-numerical-backends-gurobi) (1.1.0)

Requirement already satisfied: MarkupSafe>=0.23 in 
./local/lib/python3.7/site-packages (from 
Jinja2>=2.3->sphinx->sage-numerical-backends-gurobi) (1.1.0)

Requirement already satisfied: pytz>=0a in 
./local/lib/python3.7/site-packages (from 
babel!=2.0,>=1.3->sphinx->sage-numerical-backends-gurobi) (2018.7)

Requirement already satisfied: pyparsing>=2.0.2 in 
./local/lib/python3.7/site-packages (from 
packaging->sphinx->sage-numerical-backends-gurobi) (2.3.0)

Installing collected packages: sage-numerical-backends-gurobi

  Running setup.py install for sage-numerical-backends-gurobi ... error

Complete output from command /Users/dcoudert/sage/local/bin/python3 -u 
-c "import setuptools, 
tokenize;__file__='/private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-install-t4k429rc/sage-numerical-backends-gurobi/setup.py';f=getattr(tokenize,
 
'open', open)(__file__);code=f.read().replace('\r\n', 
'\n');f.close();exec(compile(code, __file__, 'exec'))" install --record 
/private/var/folders/l8/sxf193t11mvdyqq56f4w_6_8gn/T/pip-record-sk9om1cp/install-record.txt
 
--single-version-externally-managed --compile:

Using GUROBI_HOME obtained from gurobi.sh:

GUROBI_HOME is not set, or it does not point to a directory with a 
Gurobi installation.  Trying to link against -lgurobi

Checking whether HAVE_SAGE_CPYTHON_STRING...

Checking whether HAVE_ADD_COL_UNTYPED_ARGS...

Using compile_time_env: {'HAVE_SAGE_CPYTHON_STRING': True, 
'HAVE_ADD_COL_UNTYPED_ARGS': True}

running install

running build

running build_py

creating build

creating build/lib.macosx-10.9-x86_64-3.7

creating build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi

copying sage_numerical_backends_gurobi/__init__.py -> 
build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi

copying sage_numerical_backends_gurobi/gurobi_backend.pxd -> 
build/lib.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi

running build_ext

building 'sage_numerical_backends_gurobi.gurobi_backend' extension

creating build/temp.macosx-10.9-x86_64-3.7

creating 
build/temp.macosx-10.9-x86_64-3.7/sage_numerical_backends_gurobi

clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g 
-fwrapv -O3 -Wall -Wno-unused 
-I/Users/dcoudert/sage/local/lib/python3.7/site-packages/cysignals 
-I/Users/dcoudert/sage/local/lib/python3.7/site-p

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread Dima Pasechnik 
On Sat, 11 Jan 2020, 09:21 Antonio Rojas,  wrote:

> openblas is not being built in Sage, the system one is detected and used
> after FS#27870. FWIW, building our distro fflas-ffpack package with our
> system openblas works fine.
>

the question is why on your system it causes a problem. this setup, with
external openblas, has been tested on many different OS.


> El sábado, 11 de enero de 2020, 10:00:43 (UTC+1), Dima Pasechnik escribió:
>>
>> On Sat, Jan 11, 2020 at 8:57 AM Antonio Rojas  wrote:
>> >
>> > I don't think so - I'm pretty sure I've built it successfully after
>> that commit.
>> >
>> please compare the system openblas linkage with the one you build in
>> Sage, and post the outputs of ldd here.
>> I am pretty sure there is an interesting
>> difference, I only don't know which way.
>>
>>
>> > El sábado, 11 de enero de 2020, 9:25:04 (UTC+1), Dima Pasechnik
>> escribió:
>> >>
>> >> isn't it due to https://trac.sagemath.org/ticket/27444 - which
>> removed
>> >> --disable-openmp from fflas-ffpack flags ?
>> >> see https://trac.sagemath.org/ticket/27444#comment:34
>> >>
>> >> On Sat, Jan 11, 2020 at 7:53 AM Antonio Rojas 
>> wrote:
>> >> >
>> >> > Build fails at fflas-ffpack, log attached. Seems related to FS#27870
>> >> >
>> >> > --
>> >> > 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-...@googlegroups.com.
>> >> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/9768e0af-b10a-4721-844c-6a81832a117b%40googlegroups.com.
>>
>> >
>> > --
>> > 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-...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/488d598b-5232-4ee5-90ef-82b3ebd982fd%40googlegroups.com.
>>
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/16b2c949-712d-4c2e-9833-621da436cbb9%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3LR7pYZL-2%3D8xnYuGygoFe07uor1-S9aT25BObagU6Yw%40mail.gmail.com.

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread Antonio Rojas 
openblas is not being built in Sage, the system one is detected and used 
after FS#27870. FWIW, building our distro fflas-ffpack package with our 
system openblas works fine.

El sábado, 11 de enero de 2020, 10:00:43 (UTC+1), Dima Pasechnik escribió:
>
> On Sat, Jan 11, 2020 at 8:57 AM Antonio Rojas  > wrote: 
> > 
> > I don't think so - I'm pretty sure I've built it successfully after that 
> commit. 
> > 
> please compare the system openblas linkage with the one you build in 
> Sage, and post the outputs of ldd here. 
> I am pretty sure there is an interesting 
> difference, I only don't know which way. 
>
>
> > El sábado, 11 de enero de 2020, 9:25:04 (UTC+1), Dima Pasechnik 
> escribió: 
> >> 
> >> isn't it due to https://trac.sagemath.org/ticket/27444 - which removed 
> >> --disable-openmp from fflas-ffpack flags ? 
> >> see https://trac.sagemath.org/ticket/27444#comment:34 
> >> 
> >> On Sat, Jan 11, 2020 at 7:53 AM Antonio Rojas  
> wrote: 
> >> > 
> >> > Build fails at fflas-ffpack, log attached. Seems related to FS#27870 
> >> > 
> >> > -- 
> >> > 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-...@googlegroups.com. 
> >> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/9768e0af-b10a-4721-844c-6a81832a117b%40googlegroups.com.
>  
>
> > 
> > -- 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/488d598b-5232-4ee5-90ef-82b3ebd982fd%40googlegroups.com.
>  
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/16b2c949-712d-4c2e-9833-621da436cbb9%40googlegroups.com.

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread Dima Pasechnik 
On Sat, Jan 11, 2020 at 8:57 AM Antonio Rojas  wrote:
>
> I don't think so - I'm pretty sure I've built it successfully after that 
> commit.
>
please compare the system openblas linkage with the one you build in
Sage, and post the outputs of ldd here.
I am pretty sure there is an interesting
difference, I only don't know which way.


> El sábado, 11 de enero de 2020, 9:25:04 (UTC+1), Dima Pasechnik escribió:
>>
>> isn't it due to https://trac.sagemath.org/ticket/27444 - which removed
>> --disable-openmp from fflas-ffpack flags ?
>> see https://trac.sagemath.org/ticket/27444#comment:34
>>
>> On Sat, Jan 11, 2020 at 7:53 AM Antonio Rojas  wrote:
>> >
>> > Build fails at fflas-ffpack, log attached. Seems related to FS#27870
>> >
>> > --
>> > 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-...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-devel/9768e0af-b10a-4721-844c-6a81832a117b%40googlegroups.com.
>
> --
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/488d598b-5232-4ee5-90ef-82b3ebd982fd%40googlegroups.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0omF7h5ay%2BCCoDvKzdV3i98odKeydDcuwR%2B6tQLY2JuA%40mail.gmail.com.

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread Antonio Rojas 
I don't think so - I'm pretty sure I've built it successfully after that 
commit. 

El sábado, 11 de enero de 2020, 9:25:04 (UTC+1), Dima Pasechnik escribió:
>
> isn't it due to https://trac.sagemath.org/ticket/27444 - which removed 
> --disable-openmp from fflas-ffpack flags ? 
> see https://trac.sagemath.org/ticket/27444#comment:34 
>
> On Sat, Jan 11, 2020 at 7:53 AM Antonio Rojas  > wrote: 
> > 
> > Build fails at fflas-ffpack, log attached. Seems related to FS#27870 
> > 
> > -- 
> > 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-...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/9768e0af-b10a-4721-844c-6a81832a117b%40googlegroups.com.
>  
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/488d598b-5232-4ee5-90ef-82b3ebd982fd%40googlegroups.com.

Re: [sage-devel] 9.1.beta0 build failure on Arch

2020-01-11 Thread Dima Pasechnik 
isn't it due to https://trac.sagemath.org/ticket/27444 - which removed
--disable-openmp from fflas-ffpack flags ?
see https://trac.sagemath.org/ticket/27444#comment:34

On Sat, Jan 11, 2020 at 7:53 AM Antonio Rojas  wrote:
>
> Build fails at fflas-ffpack, log attached. Seems related to FS#27870
>
> --
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/9768e0af-b10a-4721-844c-6a81832a117b%40googlegroups.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1-a4QcQUBHenYnGyDEcFaKLw6qWCbXK8X_wC887Dd9Cw%40mail.gmail.com.

Re: [sage-devel] Re: drop python2 compatibility in 9.1 ?

2020-01-11 Thread Antonio Rojas 
El viernes, 10 de enero de 2020, 14:54:24 (UTC+1), E. Madison Bray escribió:
>
> That seems like the obvious approach to me.  As it is I've long felt 
> that Sage should be more flexible in its dependencies where 
> possible/necessary.  With most Python packages it's easy as most have 
> a .__version__ and its not so hard to define some variable 
> like IS_RPY_2 and just have two separate branches.  I have things like 
> that all over the place in other packages to support e.g. different 
> Numpy versions or work around version-specific bugs. 
>

I've opened https://trac.sagemath.org/ticket/28988 for rpy. But at this 
point the major issues are python 3.8 and ipython 7, and I don't see how 
one could support several versions of them without forking hundreds of 
doctests. Both updates require multi-thousand-lines patches, due to changes 
in dict sorting and hashes.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cade379b-146b-46c9-b057-c8b66570553b%40googlegroups.com.