Thanks for that! I was looking at the bug Dima opened in brial as the
maintainer and I was, "this is not inside stock brial code" that it
comes from m4ri makes sense to me.
François
On 20/05/2025 09:00, Antonio Rojas wrote:
The bug is in m4ri, not in brial. It is fixed in 20250128, sage
shoul
the xgap package was the guilty party causing trouble if my memory
serves me right from all those years ago. It was automatically loaded too.
I cannot remember how I figured it out now. xgap would not load by
itself these days, if it still exists.
François
On 27/03/2025 09:19, enriqu...@gmail.
he version of giac it is using?
It would be much better if it is using the system giac, but I am
still not sure
which giac it is using.
Will see if I can find more information.
--Nasser
On Sunday, January 5, 2025 at 1:20:06 AM UTC-6 François Bissey wrote:
It is very likely that sagemath installed by pacman from AUR uses the
system giac. But you can check the list of files installed by pacman for
sagemath.
pacman -Ql $package_name
if it includes a private copy of giac, it should appear in the list.
François
On 5/01/25 18:48, 'Nasser M. Abbasi' v
It is now a separate optional package
https://pypi.org/project/sagemath-bliss/
On 27/10/24 14:52, Marc Culler wrote:
A Sage_macOS user pointed out that
from sage.graphs import bliss
produces a "Module not found" error.
In SageMath 10.3 the directory
sage/venv/lib/python3.11/site-packages
On 21/08/24 13:22, Kwankyu Lee wrote:
On Wednesday, August 21, 2024 at 9:42:42 AM UTC+9 John H Palmieri wrote:
... maybe we should consider distributing all of the documentation
pre-built as a tarball, not just some png files. (I have resisted
this in the past, but I am changing my
Making all those packages optional sounds good. I am not completely sure
about playwright. It feels a bit heavy to shoehorn to produce
documentation from source. I need a bit more time to think about it.
Using binary produced documentation packages for "stable" releases is a
fine option, but p
On 3/08/24 08:06, Niranjana K M wrote:
On Sat, Aug 3, 2024 at 1:29 AM François Bissey <mailto:frp.bis...@gmail.com>> wrote:
On 3/08/24 07:17, Michael Orlitzky wrote:
> On Fri, 2024-08-02 at 07:09 -0700, Niranjana K M wrote:
>> At first I had flint-3.1.0 f
On 3/08/24 07:17, Michael Orlitzky wrote:
On Fri, 2024-08-02 at 07:09 -0700, Niranjana K M wrote:
At first I had flint-3.1.0 from Gentoo portage. Got same errors and build
failed. The I uninstalled flint and its dependents from Gentoo and let the
Sage choose its flint spkg. Again it also fail
On 16/04/24 04:41, kcrisman wrote:
SageMath has several other long-term contributors who also package
software. We're all roughly on the same page about what it would take
to fix the sage installation for end users.
And some of these people (perhaps kiwifb?) have not been as dire
If you do that from a terminal, there should be a number of messages
spat back at you before the browser start jupyterlab.
Can you post them?
François
On 28/02/24 09:41, Jan Groenewald wrote:
Hi
sage 10.2 on Debian 12, and
sage -i jupyterlab
sage --notebook=jupyterlab
launches, and the logo
From the log sent to me in a private email:
[sagelib-10.1] gcc -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1
-DNDEBUG -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall
-Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3
-Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -
Hi,
We need the build log. The last output is not always where the error
occurred. On most modern system there are several compilations done at
the same time. The last one printed is just the last one to finish.
François
On 27/10/23 20:15, Ayan Mahalanobis wrote:
Hi All,
I am trying to bui
we moved the essential bits inside sage.
Why they persisted with it, I do not know.
If people have issues, I welcome them opening them on the tracker so I
can look at them.
Nevertheless moving to newer, better maintained stuff would make my day.
François Bissey
On 2/10/23 08:29, Matthias
Never mind names, in a perfect world I want the orcid of all the
contributors who have one. In that same perfect world all sage
contributors have one.
This is scientific output and authorship and uniquely identifying
authors is what orcid is for.
https://orcid.org/
On 8/02/23 22:16, Dima Pasec
It 404 for me. I am guessing it is not public yet.
On 3/02/23 16:05, Matthias Koeppe wrote:
Only 10% of the final approach (import) are done, but the impatient can
already take a look at https://github.com/sagemath/sage/issues: The
attribution of imported issues to GitHub users and the creation
On 3/02/23 10:30, David Joyner wrote:
Hi Vincent:
Will this be recorded and posted on youtube,
or something like that?
- David
I am seconding that request. That time is 5:30am in my time zone.
François (NZST=UTC+13 at this time of the year)
--
You received this message because you are subscr
People are certainly receiving and applying. I see the number of people
in the organization growing steadily since this morning.
François
On 2/02/23 15:23, Kwankyu Lee wrote:
I received the invitation an hour ago. It worked great!
--
You received this message because you are subscribed to the
I believe it is because you have pari-2.15 and giac is not compatible
out of the box with that version of pari. There is a patch on trac for
the next giac upgrade.
François
On 20/11/22 23:10, enriqu...@gmail.com wrote:
I had the same issue, running ./configure --with-system-pari=no before
mak
On 8/11/22 07:36, Matthias Koeppe wrote:
Updated times for Europe / Africa / Americas after DST changes:
Monday noon, 12:15pm San Francisco
Monday afternoon, 3:15pm New York
Monday afternoon, 17:15 Rio de Janeiro & Santiago de Chile
Monday evening, 21:15 Paris
Monday evening, 22:15 Johannesbu
Note that New Zealand has switched to daylight saving (or from I never
remember, French call them winter time and summer time, much easier) in
the last few weeks. So, the calling time was 3:15pm for me.
I would be able to make 2:15pm, but not 3:15pm as I get a kid from
school at that time. 4:15
I am in the middle of picking a kid from school at that time so I won't
be there for that one tomorrow. Filled my bit in the pool.
On 15/09/22 06:36, Matthias Koeppe wrote:
Friday afternoon, 3:15pm Auckland (New Zealand)
François
--
You received this message because you are subscribed to the
It appears my info was all correct already. I removed my info from the
trac landing page.
I notice there is some confusion in what the label "work" means. Some
people put their position rather than their institution. I don't think
that's a big deal but if that's you :) you can fix that too.
F
The vote is now closed.
Hybrid: 8 top votes
pseudo-package: 2 top votes
copy: 0 top votes
Thanks to all voters.
François
On Wednesday, August 24, 2022 at 11:38:40 AM UTC+12 François Bissey wrote:
> Hi all,
>
> https://trac.sagemath.org/ticket/34152 needs help to decide what solut
In the interest of clarity and ease of counting for me, can we keep the
thread onto votes and possibly voting issues.
Arguments should go back to the ticket or a separate thread please.
François
On 24/08/22 12:43, Matthias Koeppe wrote:
On Tuesday, August 23, 2022 at 5:34:01 PM UTC-7 Travis S
Hi all,
https://trac.sagemath.org/ticket/34152 needs help to decide what solution
we implement going forward.
The ticket is concerned with updating the bootstrap process by removing the
current need for gettext and replacing it with gnulib (
https://www.gnu.org/software/gnulib). gnulib is not a r
https://trac.sagemath.org/ticket/33316 that’s what happened. Support for gcc
lower than 6.3 removed. I don’t know if you can get a newer gcc from that
ubuntu.
> On 22/06/2022, at 22:56, John Cremona wrote:
>
> On a machine (Ubuntu 16.04.7 LTS) on which I have done a lot of Sage
> development b
I’d seriously watch your talk (The way to a fully modularized Sage library
10.0) live and chat but I’ll be driving kids to school at that time :)
I’ll have to enjoy the replay later in the day.
François
> On 26/05/2022, at 18:57, Matthias Koeppe wrote:
>
> Preliminary program:
> https://resear
And trivial https://trac.sagemath.org/ticket/33859 is ready for review.
> On 17/05/2022, at 12:24, François Bissey wrote:
>
> Right, I’ll open a ticket for that.
>
>> On 17/05/2022, at 12:11, Matthias Koeppe wrote:
>>
>> It looks like this directory was removed
Right, I’ll open a ticket for that.
> On 17/05/2022, at 12:11, Matthias Koeppe wrote:
>
> It looks like this directory was removed in #27155, so this line can be
> removed from MANIFEST.in
>
>
> On Monday, May 16, 2022 at 4:31:50 PM UTC-7 François Bissey wrote:
> Hi,
Hi,
I have noticed it before but I have only started to wonder about it while
preparing the 9.6 release for Gentoo.
During the install phase while the wheel is being prepared I have the following
messages
listing git files failed - pretending there aren't any
warning: no files found matching '*
> On 12/05/2022, at 12:52, Matthias Koeppe wrote:
>
> On Wednesday, May 11, 2022 at 5:48:38 PM UTC-7 François Bissey wrote:
> > On 12/05/2022, at 10:54, Matthias Koeppe wrote:
> > In https://trac.sagemath.org/ticket/32406 I propose to change the default
> >
> On 12/05/2022, at 10:54, Matthias Koeppe wrote:
>
> In https://trac.sagemath.org/ticket/32406 I propose to change the default
> installation of Sage to use "configure --enable-editable".
> This has many benefits for developers: If you only make changes to Python
> files, there is no need
This is sage-devel, most people here eat sage unstable for breakfast, may be
ask in sage-support? But otherwise, yes it is overly scary. It may have been
justified 10 years ago but not so much now.
> On 2/05/2022, at 07:19, Matthias Koeppe wrote:
>
> https://www.sagemath.org/download-latest.ht
Well binary packages are not so well known in Gentoo. But in any case, your
argument about source distribution applies pretty much to all distro package
maintainers. At some point they have to choose which options they will enable
in the build, binary or otherwise, they distribute.
>From what I
https://downforeveryoneorjustme.com/trac.sagemat.org
says it’s not just you or me.
> On 15/04/2022, at 13:50, Yueqi Li wrote:
>
> Hi,
>
> I'm unable to access trac.sagemath.org. I'm wondering if it's because the
> website down?
>
> Sincerely,
> Nicole
>
> --
> You received this message bec
You do realise that those files under sage/build/pkgs and sage/pkgs are
actually symlinks to a single instance?
> On 15/04/2022, at 12:25, John H Palmieri wrote:
>
> I think your search is following some symbolic links: only three of these
> instances are under version control (git):
>
>
I can’t help but notice that part of the message:
“Warning: Identity file /Users/yueqili/.ssh/ssh_key-sage-trac-2 not accessible:
No such file or directory.”
Are you sure that it is the right file name?
François
> On 11/04/2022, at 07:23, L Nicole wrote:
>
> Hi,
>
> I have the same issue too.
The way they want to run pytest, I would suggest to try
cd src
pytest -v
first. The configuration files for pytest are in there and it should be the
reported rootdir. Not SAGE_ROOT.
> On 24/03/2022, at 22:41, Dima Pasechnik wrote:
>
> you need Sage's pytest package, which can be installed by d
Hi all,
In the old day the sagelib was outputting all the compiling and linking
commands during builds.
In the last few months, it only display progress messages and warnings from the
compiler and linker.
Is there a way to have the verbosity back? There are times where you want to
inspect the i
>From your log
OSError: [Errno 28] No space left on device
You’ve run out of disk. Nothing we can do about that :)
> On 9/03/2022, at 08:25, Ethan Lin wrote:
>
> Hello! I have encountered an error while making/upgrading sage,
> The sage version is 9.6.beta4
> My OS is Debian Bookworm (testing)
Any reason you are sticking to sage 9.0 when 9.5 is out?
> On 7/03/2022, at 10:27, Alexander Rahm wrote:
>
> This workaround fails on my computer:
>
> Using
> ./configure --without-system-libffi
> make
>
> I however run into the same crash.
>
> Best,
>
> Alexander
>
> [ecl-16.1.2.p5] make[
It looks like several things not going well. The first and most obvious one is
that libntl doesn’t seem to be found. Some of the other stuff may be related to
gmp. ntl is definitely found by configure but the location of the library is
not passed with `-L` to giac and eclib at least. So I think
HI Kotaro,
yes, it looks like the list of dependencies for trial is slightly incorrect
since brial uses pkg-config to detect m4ri.
We’ll need to open a bug on trac for this.
François
> On 26/02/2022, at 01:15, Kotaro Nishida wrote:
>
> Greetings,
>
> I am installing sage but I can't solve th
> On 14/02/2022, at 03:57, Michael Orlitzky wrote:
>
> If not, I'm proposing we,
>
> 1. Replace all direct uses of SAGE_TMP in library/doctest code with
> python's tempfile module.
> 2. Drop SAGE_TMP from tmp_filename() and tmp_dir(); this will revert
> to whatever directory the OS
Just so you don’t feel alone, it happened to me earlier this month. I almost
posted before googling the error. I have now replaced my 11 years old ssh key
by a shinny new one.
> On 20/01/2022, at 18:25, Steven Trogdon wrote:
>
> Didn't mean to send a private email. This worked, thanks. I was a
After looking a bit at gsl’s doc I don’t think there is any advantage to using
them if we are not using the error handling and reporting of gsl (by that I
mean error estimates on the results). The only interesting detail is, quoting,
“consistency across platforms”. If we are not doing high preci
Another fact that annoys me about monorepo is the versioning of the components.
There is no right or wrong here, just preferences.
In the monorepo scenario you’ll have subcomponents released and they (usually)
will all have matching version numbers.
This is easy to figure out what you should use
> On 11/10/2021, at 15:07, Matthias Koeppe wrote:
>
> On Sunday, October 10, 2021 at 5:49:05 PM UTC-7 François Bissey wrote:
> To package these I pull the full tree :( and then I don’t go to
> SAGE_ROOT/pkgs/pkg_name and build from there.
> If I want to patch it doesn
> On 11/10/2021, at 15:02, Matthias Koeppe wrote:
>
> On Sunday, October 10, 2021 at 5:49:05 PM UTC-7 François Bissey wrote:
> For proper releases, I am hoping for separate tarballs (eventually) which
> means that there won’t be any issues with symbolic links.
>
>
> On 11/10/2021, at 14:00, William Stein wrote:
>
> On Sun, Oct 10, 2021 at 5:49 PM François Bissey wrote:
>>
>> One annoying thing about monorepo from a downstream perspective - but only
>> for people crazy enough to package a development branch (OK that would b
One annoying thing about monorepo from a downstream perspective - but only for
people crazy enough to package a development branch (OK that would be me and
not many other people :) ).
The split packages have their setup.py or equivalent in SAGE_ROOT/pkgs/pkg_name
and some links to the single sag
I have at least one close user/tester that builds sage-on-gentoo on a gentoo
prefix (on a debian machine I think). Pretty much every beta/rc release get
built and tested.
I used to work on gentoo-prefix on OS X for a while. I should try it again
someday but I don’t feel like my little macbook pr
> On 24/09/2021, at 13:12, Matthias Koeppe wrote:
>
> c) The use of any Fortran compiler other than homebrew's packaging of
> gfortran on macOS (and our gfortran spkg) is completely unexplored. Given the
> instability of homebrew -- as a rolling platform on which it is not possible
> to ins
As someone who contributed to those (and literally created the gfortran package
when I pushed for enabling clang support on OS X) I welcome their demise. I’ll
review their removal with pleasure if you need it.
François
> On 24/09/2021, at 10:17, Dima Pasechnik wrote:
>
> https://trac.sagemath
s = 8
> ? print(default(datadir))
> /usr/share/pari
> ?
>
> Goodbye!
>
>
> 2021年8月9日月曜日 9:07:43 UTC+9 François Bissey:
> This is really an issue to build cypari2. Could you give us the result of the
> following:
> * start gp by typing
> gp
> * at the gp prompt
This is really an issue to build cypari2. Could you give us the result of the
following:
* start gp by typing
gp
* at the gp prompt enter
print(default(datadir))
* and send us the result.
You can use ctrl+d to exist the gp session.
François
> On 9/08/2021, at 11:46, Kazuyoshi Furutaka
> wrote:
+1
> On 17/07/2021, at 09:26, Samuel Lelievre wrote:
>
> +1
>
> --
> 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.
Yeah, I turned it off on a previous machine after a funny replacement of lapack.
> On 10/07/2021, at 22:57, Samuel Lelievre wrote:
>
> With some effort these engines can actually be turned off.
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
Should be solved by the move to penal-0.7.29. This is the same kind of errors
that I fixed for g++11.
> On 10/07/2021, at 08:06, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
>
> Dear all,
>
> I am not able to build pynac with clang because of the error
>
> error: no member named 'nume
It looks like maxima.fas has not been built. Last time I saw that happen
in sage-on-gentoo was because the patch to build it was missing.
Not sure how it could happen on your setup, the log needs further inspection.
> On 14/05/2021, at 21:18, John Cremona wrote:
>
> I have been installing sage-9
I guess I could whip up a branch quickly since we know the things that have to
be done overall.
I would prefer if we had a new pynac release rather than continue pilling
patches.
François
> On 11/05/2021, at 11:00, 'Travis Scrimshaw' via sage-devel
> wrote:
>
> +1 on this. I know many people
nst
000180b0 T Givaro::Integer::operator std::__cxx11::basic_string, std::allocator >() const
Last compile was with gcc-11.1.0
> On 8/05/2021, at 23:34, François Bissey wrote:
>
> What compiler and flags have used to compile fedora 32 givaro? Can we easily
> find out?
>
What compiler and flags have used to compile fedora 32 givaro? Can we easily
find out?
> On 8/05/2021, at 23:31, Dima Pasechnik wrote:
>
> With system Givaro, one gets
>
> [dochtml] ImportError:
> /home/scratch2/dimpase/sage/sage/local/lib64/python3.8/site-packages/sage/matrix/matrix_modn_spa
Hi all,
Do we have a fork and repo for lcalc to add our changes?
Some lcalc headers are currently preventing sage to compile with gcc-11
and rather than just adding some more patch to lcalc I was wondering
if we had made headways in using a forked repo for it since its upstream
development is pret
Mainly https://trac.sagemath.org/ticket/31578 but really
https://github.com/sagemath/sage/blob/develop/src/sage/misc/cython.py#L56
had the potential to leak that kind of stuff forever.
> On 16/04/2021, at 21:58, Dima Pasechnik wrote:
>
> Since a while I see on Gentoo (with the profile
> "default
> On 14/04/2021, at 16:52, Matthias Koeppe wrote:
>
> On Tuesday, April 13, 2021 at 9:45:19 PM UTC-7 François Bissey wrote:
>
> I guess right now I am just after sagemath-doc-src as defined on
> https://trac.sagemath.org/ticket/29868
> although I am not excluding us
> On 14/04/2021, at 16:26, Matthias Koeppe wrote:
>
> On Tuesday, April 13, 2021 at 6:28:06 PM UTC-7 François Bissey wrote:
> I am looking at moving to the modular setup for sage-on-gentoo during the 9.4
> cycle. [...]
> I now have some idea on how to build the documentation
I am looking at moving to the modular setup for sage-on-gentoo during the 9.4
cycle.
I am already experimenting and feeling stuff out.
I have already expressed concerns once about building documentation.
I now have some idea on how to build the documentation in sage-on-gentoo. But
the doc
folde
Running the doctests plong style just regularly fails for him on some machines
with
memory errors. Re-running the tests with higher limits usually works. But the
default
are obviously too low on some of his machines.
> On 24/03/2021, at 13:16, Volker Braun wrote:
>
> I don't understand what t
It has been a pain for Steve Trogdon in sage-on-gentoo on an ongoing basis
ever since it was included. I have somehow been blessed with enough RAM on
all my dev machines. You sum and articulate my position on the matter quite
nicely and even with additional bullet points (the last three are really
> On 19/03/2021, at 23:05, 'jonatha...@googlemail.com' via sage-devel
> wrote:
>
> We configure libaries with e.g. `--with-zlib="$SAGE_LOCAL"` unconditionally.
> Why would this succeed, if we use the systems `zlib`?
>
It depends a bit on whether you use a properly written configure script
You have the gist of it. There are various environment variables that can
suppress or enable
the use of sage as a back for multi-precision numbers. Historically that
sometime caused trouble
in sympy as well.
> On 19/03/2021, at 05:28, Nils Bruin wrote:
>
> Am I understanding correctly that "i
Hi all,
I was wondering if there was a way to figure if a module from one
package is imported from another one and which one at that.
This is quite relevant to sage-on-distros. mpmath-1.2.0+ tries
to figure out if it is called from sage by detecting if SAGE_ROOT
is defined. Assuming that if it is
> On 12/03/2021, at 12:14, Matthias Koeppe wrote:
>
> On Thursday, March 11, 2021 at 3:07:41 PM UTC-8 François Bissey wrote:
>
> > On 12/03/2021, at 11:48, Matthias Koeppe wrote:
> When are we going to start seeing separate sdist tarballs? That’s really the
> poin
> On 12/03/2021, at 11:48, Matthias Koeppe wrote:
>
> No, there's nothing wrong with it; this is the normal way to use the
> repository now and in the planned future.
> After running ./bootstrap, the source tree contains several self-contained
> Python distribution package source trees in b
> On 12/03/2021, at 11:20, Matthias Koeppe wrote:
>
> Well, autotools does not even have a mechanism to advertise
> dependencies/requirements -- other than "configure" exiting with an error if
> they are not satisfied. You as a downstream package maintainer declare and
> update the requirem
> On 12/03/2021, at 11:20, Matthias Koeppe wrote:
>
> And then -- of course likely not relevant for gentoo -- there is also the
> distinction between source and binary distributions (wheels): For the package
> itself, many users have a good reason to build it from source; but for a
> separa
> On 12/03/2021, at 09:46, Matthias Koeppe wrote:
>
> On Wednesday, March 10, 2021 at 8:18:11 PM UTC-8 Nathan Dunfield wrote:
> On Wednesday, March 10, 2021 at 4:50:41 AM UTC-6 Dima wrote:
> numpy does this:
> https://numpy.org/devdocs/docs/howto_build_docs.html
>
> you can only build numpy d
> On 12/03/2021, at 09:41, Matthias Koeppe wrote:
>
> On Thursday, March 11, 2021 at 11:36:18 AM UTC-8 Antonio Rojas wrote:
> Here is my current PKGBUILD (after some cleanup I did today)
> https://github.com/archlinux/svntogit-community/blob/packages/sagemath-doc/trunk/PKGBUILD
> I'm building
> On 11/03/2021, at 05:03, Matthias Koeppe wrote:
>
> On Wednesday, March 10, 2021 at 1:21:07 AM UTC-8 François Bissey wrote:
> [...] building the documentation [...]
>
> In https://trac.sagemath.org/ticket/29868 I sketch a design that is in line
> with modern
> On 11/03/2021, at 01:10, Antonio Rojas wrote:
>
> El miércoles, 10 de marzo de 2021 a las 10:21:07 UTC+1, François Bissey
> escribió:
> Instead of trying to fix the problem that you should be building the
> documentation
> before installing, the push to modularisat
> On 10/03/2021, at 23:50, Dima Pasechnik wrote:
>
> On Wed, 10 Mar 2021, 09:21 François Bissey, wrote:
> So the situation is now:
> * install package A
> * install package B
> * make a package C that takes B and applies it to the install of A and install
> the d
Hi all,
So today I will be talking about subject that I in sage-on-gentoo have
brushed under the carpet for years focusing on helping to be able to
use more and more components of the system and ultimately get “sagelib”
to be one such component.
Sagemath as a meta distribution of stuff has bad ha
And we already fixed it in https://trac.sagemath.org/ticket/31127
which should be in the next beta.
> On 12/01/2021, at 8:46 AM, Dima Pasechnik wrote:
>
> it's a bug introduced in
> 26032b18f9b (Martin Albrecht 2020-12-15 12:12:14 + 11)
> [fplll == 5.4]
>
> it should be '=', not
Hi all,
This is the time of the year where I go for a few days of internet detox.
No reviews or contributions from me until next Monday.
Cheers,
François
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop rec
> On 7/12/2020, at 10:25 PM, Antonio Rojas wrote:
>
> El lunes, 7 de diciembre de 2020 a las 6:11:31 UTC+1, Matthias Koeppe
> escribió:
> In https://trac.sagemath.org/ticket/30315 I propose to make jmol optional. To
> my understanding it has been replaced by generally better options such as
18:00 UTC is 7:00am the next day for me. What with dropping kids to school, I
probably won’t show up
until 20:00 UTC.
> On 6/12/2020, at 2:47 PM, Matthias Koeppe wrote:
>
> A preliminary schedule is now posted.
>
>
> On Sunday, November 22, 2020 at 11:41:01 AM UTC-8 Matthias Koeppe wrote:
> S
Also suitesparse.
Of course one of thing is actually blas/lapack (openblas)- but
with any luck we can use the accelerate framework from OS X.
I haven’t heard it is not available on macs with M1 chips so I am
assuming it is present.
> On 25/11/2020, at 3:46 PM, kcrisman wrote:
>
>
>
> IMHO it
That would be a new fortran compiler. I did builds in the past with
the intel fortran compiler and the PG compiler but not NAG.
You’ll be in totally uncharted territory.
Fraçois
> On 25/11/2020, at 5:36 AM, Dima Pasechnik wrote:
>
> Anyhow, there is
> https://www.nag.com/news/first-fortran-com
It is a very interesting memory management problem.
Wish I could find the bottom of it.
https://github.com/cschwan/sage-on-gentoo/issues/610
> On 23/11/2020, at 10:59 PM, Dima Pasechnik wrote:
>
> On a Gentoo machine I got the toolchain broken in an interesting way:
> I get errors such as
>
> I
Well it certainly wasn’t changed each time we upgraded MPL (and yes I am part
of the guilty) as it should have.
François
> On 14/11/2020, at 7:05 AM, Matthias Koeppe wrote:
>
> We have some suspicious code in src/bin/sage-env; perhaps this is a good
> opportunity to review whether this should
The top of your crash log is interesting, especially with the context you give
it.
[I 08:54:47.064 NotebookApp] 302 GET
/?token=9646f700a842467835ef92b578ebef632e86a326a85e828b (127.0.0.1) 1.53ms
[I 08:54:56.520 NotebookApp] Kernel started:
d273c9d9-80cb-45a6-a336-b3562f294b26, name: sagemath
-
libqd.a in your /usr/local/lib folder has been compiled without -fPIC and cannot
be used to build a shared library.
As stated by Dima, you shouldn’t need to install your own. If you insist on
using
a libqd from /usr/local/lib, install one compiled with -fPIC.
François
> On 13/11/2020, at 10:40 A
That’s a gcc-10 porting issue. I thought the fix from upstream had been applied.
Someone more familiar with the ticket should comment.
> On 28/10/2020, at 12:22 PM, 'Peter Mueller' via sage-devel
> wrote:
>
> On a Lenovo ThinkPad with an up to date Manjaro Linux OS and Sage 9.2
> successfully
That’s nice but it looks like there could be improvement to the authors’ list.
Some people appear by handle rather than name. Is it because they don’t give
their real
names on GitHub? Or don’t have a GitHub account? It also looks truncated.
> On 7/10/2020, at 9:46 AM, Dima Pasechnik wrote:
>
>
I have just posted some musing on the issue on GitHub.
> On 23/09/2020, at 10:28 PM, Antonio Rojas wrote:
>
>
>
>
> There is also something funny with Flint 2.6 build using cmake - not
> sure if it's the case on your system, but it seems
> that in this case there is no way to specify whethe
I cannot talk for all distress but in Gentoo (and I believe at least arch) I
build everything
as system packages. Which means that some have to be a particular version or
include specific
patches.
The sagemath library - the python stuff - is then built and installed as a
regular python package.
You are probably experiencing https://trac.sagemath.org/ticket/30351
> On 18/08/2020, at 12:28 PM, Zachary Scherr wrote:
>
> I tried to build the documentation on 9.2 beta 8 and the documentation
> building seems to get hang on:
>
> [dochtml]
> [dochtml] [thematic_] building [html]: targets fo
Looks like a missing makeinfo problem. I thought we had a fix for that included.
But I only poorly followed the ecl upgrade ticket due to other commitments.
> On 19/07/2020, at 12:50 PM, David Einstein wrote:
>
> Attempting to rebuild sage I run into problems building ecl. This baffles
> me, a
1 - 100 of 818 matches
Mail list logo
