In Fedora 40 I encountered one error building the documentation, because it
did not find libflint.so.18 (it is now libflint.so.19). I got two
solutions: symbolic link of libflint.so.19 to libflint.so.19, or complete
rebuild.
The test passed for src/sage/libs/gap/element.pyx and had the
There are some pacthes to be applied (explained in the issue) and then it
is built with system gcc
El domingo, 5 de mayo de 2024 a las 1:05:55 UTC+2, Volker Braun escribió:
> I get the same, there is an issue at
> https://github.com/sagemath/sage/issues/37698
>
> On Sunday, May 5, 2024 at
In my config.log it says that it tries to install ppl since gcc is built.
No ppl package in fedora 39
El sábado, 4 de mayo de 2024 a las 13:26:48 UTC+2, Dima Pasechnik escribió:
> I guess you might be missing gmp-c++ system package.
> Please install it and try again. It seems we need to look at
In a test installation of Fedora 40, I have the same issue, solved
installing gmp package, but then doc has a problem with libharfbuzz. On the
other side trying to install it with gcc 14 fails with sagelib
El sábado, 4 de mayo de 2024 a las 11:27:23 UTC+2, jaap...@gmail.com
escribió:
> On
In rc2 and Fedora 39, I had the same issue. With rc3 and Fedora 39, also,
but with python 3.11, it is OK. May it be related to python 3.12 from
system?
Enrique
El miércoles, 6 de marzo de 2024 a las 13:02:02 UTC+1, jaap...@gmail.com
escribió:
> Operating System: Fedora Linux 39
> Kernel
In Fedora 39 make ptestelong gave only failure for `src/sage/tests/cmdline.py`
due to `rst2ipynb` (not new). But when running sage in the terminal I get:
```
/usr/local/sage/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/prompt_toolkit/application/application.py:988:
I guess the snappy problem is related to Fedora 37. A tricky solution is
given by upstream team in https://github.com/3-manifolds/SnapPy/issues/88
El jueves, 19 de enero de 2023 a las 13:01:18 UTC+1, Enrique Artal escribió:
> I tried in another computer with the system package (3.1
ong with Fedora's 37 Python3? (3.11.0, right?)
> What error do you see in config.log - which tells, hopefully, why it
> does not want system's python3 ?
>
> On Thu, Jan 19, 2023 at 9:43 AM Enrique Artal wrote:
> >
> > In Fedora 37 I needed to `make distclean` and use the
In Fedora 37 I needed to `make distclean` and use the sage package for
python3 and not the system one. The optional package snappy does not
compile. Anyway, thanks for the new version. Best, Enrique.
El jueves, 19 de enero de 2023 a las 0:48:25 UTC+1, Volker Braun escribió:
> As always, you
In Fedora 35 it builds applying https://trac.sagemath.org/ticket/32828 and
the proposed solution of https://trac.sagemath.org/ticket/32576
El sábado, 13 de noviembre de 2021 a las 18:36:05 UTC+1,
matthia...@gmail.com escribió:
> On Friday, November 12, 2021 at 2:58:48 PM UTC-8 Volker Braun
I have the develop version installed in two computers with Fedora 34. On
one of them, the update was successful, but in the second one, since it did
not start I erased the installation and clone the git repository again.
This is the result:
Checking whether SageMath should install SPKG gp2c...
I had the same error with this package and py in Fedora 34 (though in one
computer I had no problem); rebuilding after make distclean was OK
El martes, 22 de junio de 2021 a las 12:25:54 UTC+2,
jonatha...@googlemail.com escribió:
> Thanks Volker for the new release.
>
> Unfortunatly,
I would prefer to use gcc 11, but forcing it with configure did not work.
El sábado, 1 de mayo de 2021 a las 20:57:38 UTC+2, Dima Pasechnik escribió:
>
>
> On Sat, 1 May 2021, 15:20 Enrique Artal, wrote:
>
>> I have tried to compile it in Fedora 34, I know it is a very
After some extra trial make build after
./configure --with-system-zeromq=no --with-system-eclib=no
--with-system-flint=no --with-system-flintqs=no --with-system-ntl=no
--with-system-libgd=no --with-system-brial=no
works
El sábado, 1 de mayo de 2021 a las 16:20:01 UTC+2, Enrique Artal escribió
I have tried to compile it in Fedora 34, I know it is a very recent release
and problems would be expected. The first one is that F34 uses gcc11 and it
seems to be incompatible with sage, so when installing it uses gcc 9.2
package. After some problems I decided to run `make distclean` for a
It worked for me too!
El martes, 12 de mayo de 2020, 7:55:04 (UTC+2), Matthias Köppe escribió:
>
> On Sunday, May 10, 2020 at 3:40:28 PM UTC-7, Matthias Köppe wrote:
>>
>> On Sunday, May 10, 2020 at 12:44:01 PM UTC-7, Matthias Köppe wrote:
>>>
>>>
>>> I think the best course of action to support
Now I read it more carefully, I did the config in the wrong directory
El martes, 12 de mayo de 2020, 18:59:46 (UTC+2), Matthias Köppe escribió:
>
> On Tuesday, May 12, 2020 at 9:51:15 AM UTC-7, Enrique Artal wrote:
>>
>> I am trying to check this thicket and also #29672. This is
I am trying to check this thicket and also #29672. This is the output of git
trac checkout 29674. What am I doing wrong?
Loading ticket #29674...
Checking out Trac #29674 remote branch
u/mkoeppe/fedora_32__building_gcc__9_2_0__spkg_fails_with_gcc_10 -> local
branch
Thanks!
El domingo, 10 de mayo de 2020, 21:35:45 (UTC+2), Dima Pasechnik escribió:
>
> On Sun, May 10, 2020 at 8:10 PM Matthias Köppe > wrote:
> >
> > On Sunday, May 10, 2020 at 12:06:18 PM UTC-7, Enrique Artal wrote:
> >>
> >> Two of the failed packa
PM UTC-7, Enrique Artal wrote:
>>
>> I tried, but the compilation of gcc failed. I will try again to put the
>> logs.
>>
>>>
>>>
> Ah ok, now I see that you had said that in your original message.
>
> I think the best course of action to suppor
Last version of scipy was most probably compiled before upgrading to Fedora
32
El domingo, 10 de mayo de 2020, 21:00:09 (UTC+2), Dima Pasechnik escribió:
>
> On Sun, May 10, 2020 at 7:51 PM Matthias Köppe > wrote:
> >
> > On Sunday, May 10, 2020 at 11:41:17 AM UTC-7, Dima Pasechnik wrote:
>
Two of the failed packages, palp and sympow exist in Fedora 32. Does it
help?
El domingo, 10 de mayo de 2020, 20:50:33 (UTC+2), Matthias Köppe escribió:
>
> On Sunday, May 10, 2020 at 11:29:08 AM UTC-7, Enrique Artal wrote:
>>
>> I am using Fedora 32 with gcc 10. Upgrading to
I tried, but the compilation of gcc failed. I will try again to put the
logs.
El domingo, 10 de mayo de 2020, 20:50:33 (UTC+2), Matthias Köppe escribió:
>
> On Sunday, May 10, 2020 at 11:29:08 AM UTC-7, Enrique Artal wrote:
>>
>> I am using Fedora 32 with gcc 10. Upgrading to
I am using Fedora 32 with gcc 10. Upgrading to rc3 worked because
apparently no incompatible package changed. I could not upgrade to rc4 and
because of scipy, trying to downgrade to rc3 didn't work either. After a
dist-clean I tried with the gcc package to avoid those problems but it did
not
Python3, yes. I put the output of gdb below
El jueves, 10 de mayo de 2018, 8:27:56 (UTC+2), Dima Pasechnik escribió:
>
> Well, fire up gdb, look at the place it crashes...
>
> It is python3, right? So it would help to see what F28 does with python3,
> and why it works outside of sage.
>
with other packages including python2. The same thing happened with
the develop branch. I guess that the problem is only related to the
distribution but I am unable to guess how.
El miércoles, 9 de mayo de 2018, 7:50:11 (UTC+2), Enrique Artal escribió:
>
> Thanks! Do you have any clue abo
Thanks! Do you have any clue about why crypt module cannot be loaded?
El miércoles, 9 de mayo de 2018, 0:07:34 (UTC+2), Volker Braun escribió:
>
> Binaries are now on the way to the mirrors...
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-release"
ld try setting the environment variable SAGE_INSTALL_GCC=yes to
> force Sage to build its own version of gcc.
>
>
> On Monday, May 7, 2018 at 6:56:53 AM UTC-7, Enrique Artal wrote:
>>
>> I have tried, but there are too many dependences. I will wait for
>> binaries. I tried
using gcc-8.0.1 - this is not (yet) supported - perhaps it's known
> to Python people this this does not work...
> Can you install gcc-7 and make it the default compiler?
>
> On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote:
>>
>> I was unable to compile it
either (with
those limitations). Moreover,
the binary distribuion worked in the command line and jupyter notebook, but
not for sage-notebook.
El jueves, 24 de marzo de 2016, 11:19:58 (UTC+1), Enrique Artal escribió:
>
> More precisely, after building and using sagenb I get:
>
> Tra
the way, I
rebuilt 7.0 for testing reasons with no problem.
El miércoles, 23 de marzo de 2016, 19:26:13 (UTC+1), HG escribió:
>
> I wonder if it's not a problem with doc
> I would do : make doc-clean && make -jxx (number of cores +1) but you
> must know it will take some
I am new in this group, and I would like to thanks your efforts. I
installed successfully sage 7.1 in my personal desktop and laptop
computers. We have also two servers for teaching; in one of them everything
went OK, compiled with ssl support. But in the other server, I tried
several times
32 matches
Mail list logo
