😳
2021年6月23日(水) 7:57 Volker Braun :
> I'm running Fedora 34 and 9.4.beta3 builds fine (x86_64). It did compile
> the included gcc.
>
>
>
>
> On Tuesday, June 22, 2021 at 11:50:00 PM UTC+2 dim...@gmail.com wrote:
>
>>
>>
>> On Tue, 22 Jun 2021, 22:16 Kazuyoshi Furutaka,
>> wrote:
>>
>>> On the ot
I'm running Fedora 34 and 9.4.beta3 builds fine (x86_64). It did compile
the included gcc.
On Tuesday, June 22, 2021 at 11:50:00 PM UTC+2 dim...@gmail.com wrote:
>
>
> On Tue, 22 Jun 2021, 22:16 Kazuyoshi Furutaka,
> wrote:
>
>> On the other hand, build of gcc-10.3 failed. Then, what to d
On Tue, 22 Jun 2021, 22:16 Kazuyoshi Furutaka,
wrote:
> On the other hand, build of gcc-10.3 failed. Then, what to do?
>
use another compiler.
e.g. you can use clang
dnf install clang
then run Sages configure as follows
CC=clang CXX=clang++ ./configure
and then
make
This configuration i
On the other hand, build of gcc-10.3 failed. Then, what to do?
Kazuyoshi
2021年6月23日(水) 5:40 Dima Pasechnik :
> Sage is not yet ready to be built with gcc 11, see
> https://trac.sagemath.org/ticket/31786
>
> On Tue, Jun 22, 2021 at 8:36 PM Kazuyoshi Furutaka
> wrote:
> >
> >
> >
> > 2021年6月23日
Sage is not yet ready to be built with gcc 11, see
https://trac.sagemath.org/ticket/31786
On Tue, Jun 22, 2021 at 8:36 PM Kazuyoshi Furutaka
wrote:
>
>
>
> 2021年6月23日(水) 0:06 Dima Pasechnik :
>>
>> On Tue, Jun 22, 2021 at 3:45 PM Kazuyoshi Furutaka
>> wrote:
>> [...]
>> > First of all, I'd like
2021年6月23日水曜日 0:06:44 UTC+9 dim...@gmail.com:
> On Tue, Jun 22, 2021 at 3:45 PM Kazuyoshi Furutaka
> wrote:
> [...]
> > First of all, I'd like to let you know that on Fedora-34 (x86_64), the
> simple build (configured with --prefix only) of prestine gcc-10.3.0 fails
> without the static ve
2021年6月23日(水) 0:06 Dima Pasechnik :
> On Tue, Jun 22, 2021 at 3:45 PM Kazuyoshi Furutaka
> wrote:
> [...]
> > First of all, I'd like to let you know that on Fedora-34 (x86_64), the
> simple build (configured with --prefix only) of prestine gcc-10.3.0 fails
> without the static version of libstdc+
sagelib-9.4.beta1 error is just an uncleaned log file.
Do you build Python3 and not use one from the system?
(this would have avoided a potential problem building python)
You can post details of errors from logs/install.log, and your changes as a
diff or a link to
git branch somewhere (say, on gi
Hi all,
I'm attempting to rebuild sage by running ```make``` in order to test some
edits to the source code (```./sage``` was working before).
However, ```make``` shows that 3 packages failed to build:
Error building Sage.
The following package(s) may have failed to build (not necessarily
Hello all,
The following code currently fails:
sage: K. = GF(2)[]
sage: lcm(K(0), K(0))
In polynomial element, the lcm code attempts to divide by the gcd of the
two polynomials, throwing a zero division error in this case. One possible
fix would be to add a try except block to lcm in polynomia
On Tue, Jun 22, 2021 at 3:45 PM Kazuyoshi Furutaka
wrote:
[...]
> First of all, I'd like to let you know that on Fedora-34 (x86_64), the simple
> build (configured with --prefix only) of prestine gcc-10.3.0 fails without
> the static version of libstdc++ library (please read this thread for deta
Then, upon hitting ctrl-c I see
something like
[fplll-5.4.1] app.download_tarball(args.url_or_tarball,
args.destination, args.allow_upstream)
[fplll-5.4.1] File
"/home/dima/sage/dev/sage/build/bin/../sage_bootstrap/download/app.py",
line 41, in download_tarball
[fplll-5.4.1] tarball.down
How exactly two copies of BLAS are harmful (provided that numpy always
uses its own, and it is not used by the other potential users)?
I imagine wheels mechanics is guaranteeing this - otherwise it will
break everything, not just Sage.
On Mon, Jun 21, 2021 at 6:46 PM Matthias Koeppe
wrote:
>
>
13 matches
Mail list logo
