scipy update to 1.5.1 is now at https://trac.sagemath.org/ticket/29766

For gcc 10 support of the whole sage distribution we need at least one more 
package upgrade: sympow https://trac.sagemath.org/ticket/3360  
<https://trac.sagemath.org/ticket/3360>

Meta-ticket on gcc 10 at https://trac.sagemath.org/ticket/29456

On Saturday, July 4, 2020 at 6:18:20 PM UTC-7, Zachary Scherr wrote:
>
> Seems to be related to https://github.com/scipy/scipy/issues/11611 and as 
> was pointed out above was fixed in version 1.5.
>
> I'd like to propose two workarounds for people who can no longer build 
> sage and stumble into this thread (either should allow scipy 1.2.3 to build)
>
> 1). Use fortran 9:
>
> brew install gcc@9
> FC=gfortran-9 ./configure
> make
>
> 2). Add a flag to fortran 10 (should work if you have gcc 10 regardless of 
> whether you have homebrew or not):
>
> ./configure
> FFLAGS=-fallow-argument-mismatch make
>
> On Saturday, July 4, 2020 at 7:48:43 PM UTC-4 hel...@potuz.net wrote:
>
>> On Jul 04, Dima Pasechnik wrote: 
>> >I guess this is due to gfortran 10. 
>> >We still do not support gcc 10, I think. 
>> >Can you downgrade it to gfortran 9? 
>> > 
>> For what its worth, here running arch, 
>>
>> 1) removing line 153 from build/pkgs/gcc/spkg-configure.m4 
>> 2) adding a newer scipy: upstream/scipy-1.5.0.tar.gz 
>> 3) pulling pybind11 from this commit 
>>
>> https://git.sagemath.org/sage.git/commit/?id=fa20111935c171f1d99c410110967350f4facea2
>>  
>>
>> allowed me to upgrade without a glitch so far 
>>
>> R. 
>> > 
>> >On Sat, 4 Jul 2020, 23:06 Daniel Bump, <[1]dwb...@gmail.com> wrote: 
>> > 
>> > 
>> > 
>> > On Saturday, July 4, 2020 at 2:52:06 PM UTC-7, Dima Pasechnik wrote: 
>> > 
>> > Please post top config.log and also the full logs/pkgs/scipy-...log 
>> > 
>> > 
>> > Attached. 
>> > 
>> > Thanks, 
>> > Dan  
>> > 
>> > -- 
>> > 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 [2]sage-devel+...@googlegroups.com. 
>> > To view this discussion on the web visit [3]
>> https://groups.google.com/d/ 
>> > msgid/sage-devel/117843bf-3793-47fb-a952-9e58ad31da9co%
>> 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 [4]sage-devel+...@googlegroups.com. 
>> >To view this discussion on the web visit [5]
>> https://groups.google.com/d/msgid/ 
>> >sage-devel/ 
>> >CAAWYfq0cbnv0%3DpMchh2pPmnR%2BxaC_vVjB_Ve9NOmoJUtiLtEkQ%40mail.gmail.com. 
>>
>> > 
>> >References: 
>> > 
>> >[1] mailto:dwb...@gmail.com 
>> >[2] mailto:sage-devel+...@googlegroups.com 
>> >[3] 
>> https://groups.google.com/d/msgid/sage-devel/117843bf-3793-47fb-a952-9e58ad31da9co%40googlegroups.com?utm_medium=email&utm_source=footer
>>  
>> >[4] mailto:sage-devel+...@googlegroups.com 
>> >[5] 
>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0cbnv0%3DpMchh2pPmnR%2BxaC_vVjB_Ve9NOmoJUtiLtEkQ%40mail.gmail.com?utm_medium=email&utm_source=footer
>>  
>>
>

-- 
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/043b9acd-2017-4c43-b72d-b5bb89b82fa4o%40googlegroups.com.

Reply via email to