Hmm. I decided my previous experiment was contaminated because I slightly
messed up had to do ``make distclean`` a couple of times, so I created
three clean folders and ran precisely the above commands and nothing else,
and got a successful installation of sagemath for each of python3.10,
pytho
On Sat, Jan 11, 2025 at 8:08 AM Pavel Galashin wrote:
>
> I ran the same commands from scratch in new folders:
>
> $ git clone -c core.symlinks=true --filter blob:none \ --origin upstream
> --branch develop --tags \ https://github.com/sagemath/sage.git $ cd sage $
> make configure $ source ./.ho
I ran the same commands from scratch in new folders:
$ git clone -c core.symlinks=true --filter blob:none \ --origin upstream
--branch develop --tags \ https://github.com/sagemath/sage.git $ cd sage $
make configure $ source ./.homebrew-build-env $ ./configure
--with-python=`which pythonX.X` $
It would be great if you tried newer Homebrew Pythons, .i.e. 3.10 and 3.11,
too, and reported here the results.
On Thursday, January 9, 2025 at 10:52:07 AM UTC-6 pgal...@gmail.com wrote:
> It was installed via homebrew, same as python3.12:
> $ which python3.9 /opt/homebrew/bin/python3.9
>
>
>
It was installed via homebrew, same as python3.12:
$ which python3.9 /opt/homebrew/bin/python3.9
On Thursday, January 9, 2025 at 7:59:39 AM UTC-8 dim...@gmail.com wrote:
> Thanks. So, what's the output of
>
> which python3.9
> in your case? And where does it come from? I suppose the issue lie
Thanks. So, what's the output of
which python3.9
in your case? And where does it come from? I suppose the issue lies in
multiptocessing/multithreading support in Python, which eveloved a lot
since 3.9.
More Pythons to try might be from https://www.python.org/downloads/ (it
would be good to k
Huh, the problem got completely solved just by switching to Python 9!
Thanks a lot for the help!
$ make distclean $ ./configure --with-python=`which python3.9` $ make -s V=0
-j1
...
[tzlocal-5.0.1] installing. Log file:
/Users/user/sage/sage/logs/pkgs/tzlocal-5.0.1.log [tzlocal-5.0.1]
succ
That doesn't seem to help:
[sagemath_doc_html-none] Setting up build directory
/Users/user/sage/sage/local/var/tmp/sage/build/sagemath_doc_html-none
[sagemath_doc_html-none] Host system: Darwin PG-Mac-2.local 24.2.0 Darwin
Kernel Version 24.2.0: Fri Dec 6 19:03:40 PST 2024;
root:xnu-11215.61.5
Our docbuilder isn't great, it uses some custom outdated tricks for
parallel building. Switching to a more standard sphinx setup is overdue...
Try cleaning docs by
make doc-clean
and then run
make -j1
On Tuesday, January 7, 2025 at 2:56:47 AM UTC-6 pgal...@gmail.com wrote:
> Thank you for th
To expand on Dima's answer: Homebrew's Python 3.13 is too new to build
Sage, so Sage will reject it. The built-in Python 3.9 is, as Dima says, no
good for use with Sage. So install Homebrew's python 3.12, do "make
distclean", and then use
./configure --with-python=" fill in path to python3.1
/usr/bin/python3 you end up using is no good for using with Sage (and
unfortunately our
./configure doesn't see it), that's why.
I suggested to install python3.12 in Homebrew and use it instead.
(because building Sage's python is broken on your macOS version, too,
there aren't many other
easy opt
On Sat, Jun 1, 2024 at 7:18 PM Matthias Koeppe wrote:
>
> I'll share some additional facts for everyone's convenience.
>
> The total size of these 5 wheel packages to be added in
> https://github.com/sagemath/sage/pull/37301is about 500 kilobytes. (As a
> comparison, that's 10% of the size of ou
On 4 January 2024 12:15:07 WET, Emmanuel Charpentier
wrote:
>
>
>Indeed :
>(%i29) domain:complex; (%o29) complex (%i30) Sol1C:solve(Sys1, Unks);
>(%o30) [[x = 8,y = -40/3,l = (2*25^(1/3))/(3*9^(1/3))]] (%i31)
>Sol2C:solve(Sys2, Unks); (%o31) [] (%i32) map(lambda([w], map(lambda([v],
>subst(
On Thu, 4 Jan 2024 at 12:15, Emmanuel Charpentier
wrote:
>
> But this does not explain whiy Sage is uneble o check (numericalmlmy or
> otherwise) the solutions given by Sympy or Mathematica, which check in Sympy
> (I didn’t yet try to check them in Mathematica, the limitations of the
> current
Indeed :
(%i29) domain:complex; (%o29) complex (%i30) Sol1C:solve(Sys1, Unks);
(%o30) [[x = 8,y = -40/3,l = (2*25^(1/3))/(3*9^(1/3))]] (%i31)
Sol2C:solve(Sys2, Unks); (%o31) [] (%i32) map(lambda([w], map(lambda([v],
subst(w, v)), map(lambda([u], ratsimp(lhs(u)-rhs(u))), Sys1))), Sol1C);
(%o32
You can get the same errors from pure Maxima if you set domain to "complex",
no?
On Thursday, January 4, 2024 at 10:29:56 AM UTC Emmanuel Charpentier wrote:
> The problem seems Sage-specific : the same systems solve correctly (up to
> numerical noise) in “pure” Maxima :
> ;;; Loading #P"/usr/li
The problem seems Sage-specific : the same systems solve correctly (up to
numerical noise) in “pure” Maxima :
;;; Loading #P"/usr/lib/x86_64-linux-gnu/ecl-21.2.1/sb-bsd-sockets.fas" ;;;
Loading #P"/usr/lib/x86_64-linux-gnu/ecl-21.2.1/sockets.fas" Maxima 5.46.0
https://maxima.sourceforge.io usi
Another quick solution (cherry-picked from the PR I mentioned) would be to
change the first line of build/pkgs/editables/dependencies from
| $(PYTHON_TOOLCHAIN) $(PYTHON)
to
| flit_core $(PYTHON)
On Saturday, December 16, 2023 at 6:45:44 AM UTC-8 Heiko Knospe wrote:
> Hi,
>
> same build
Hi,
same build problem with flit_core for sage 10.3.b2 on Debian 11:
[editables-0.5] Thread model: posix
[editables-0.5] Supported LTO compression algorithms: zlib zstd
[editables-0.5] gcc version 10.2.1 20210110 (Debian 10.2.1-6)
[editables-0.5] *
On Fri, Dec 15, 2023 at 3:04 PM John H Palmieri
wrote:
> In sage-release, Matthias pointed to missing dependencies for editables,
> fixed in https://github.com/sagemath/sage/pull/36885. Maybe you can just
> do "make flit_core" (to build the missing dependency) and then "make".
>
That works, than
In sage-release, Matthias pointed to missing dependencies for editables,
fixed in https://github.com/sagemath/sage/pull/36885. Maybe you can just do
"make flit_core" (to build the missing dependency) and then "make".
On Friday, December 15, 2023 at 10:52:10 AM UTC-8 David Joyner wrote:
> Hi:
>
You should email sage-support (cc'd). This list is for teaching with sage.
On Fri, Dec 8, 2023, 2:37 PM Taylors SC wrote:
> When I would open the Sage app, it would open an Jupyter notebook in a
> Chrome window. Now when I open the Sage app, it opens a browser window, but
> it has the message "T
On Thursday, June 1, 2023 at 3:13:18 PM UTC-4 Jan Groenewald wrote:
On Thu, 1 Jun 2023 at 21:05, Luis Finotti wrote:
Interestingly enough, I have another computer, also running Debian Sid, but
a much older installation, in which Sage-10.0 *does* work in Jupyter lab.
In this one, when I look
On Thu, 1 Jun 2023 at 21:05, Luis Finotti wrote:
> Interestingly enough, I have another computer, also running Debian Sid,
> but a much older installation, in which Sage-10.0 *does* work in Jupyter
> lab. In this one, when I look at os.eviron, I also do not have
> LD_LIRBRARY_PATH...
>
And whic
Interestingly enough, I have another computer, also running Debian Sid, but
a much older installation, in which Sage-10.0 *does* work in Jupyter lab.
In this one, when I look at os.eviron, I also do not have
LD_LIRBRARY_PATH...
On Thursday, June 1, 2023 at 1:54:06 PM UTC-4 Luis Finotti wrote:
On Thursday, June 1, 2023 at 12:46:33 PM UTC-4 Nils Bruin wrote:
I don't think jupyter cares about givaro. However, it sounds like your
jupyter sets up some things about the library search path (perhaps an
LD_LIBRARY_PATH)? that gets inherited by the sage process that gets
subsequently run
Sounds like RPATH has to used somewhere to make sure the correct dynamic
library is used.
On Thu, 1 Jun 2023, 17:46 Nils Bruin, wrote:
> On Thursday, 1 June 2023 at 07:29:27 UTC-7 Luis Finotti wrote:
>
>
> I am not sure I will miss them (and other packages that depended on it --
> fflas-ffpack
On Thursday, 1 June 2023 at 07:29:27 UTC-7 Luis Finotti wrote:
I am not sure I will miss them (and other packages that depended on it --
fflas-ffpack libgivaro-dev libgivaro9 liblinbox-dev python3-brial
python3-sage), but isn't there a way to force Jupyter to use Sage's one?
I don't think ju
On Thursday, June 1, 2023 at 4:55:57 AM UTC-4 Nils Bruin wrote:
the line:
calling init: /usr/lib/x86_64-linux-gnu/libgivaro.so.9
is definitely indicating that you are picking up a system libgivaro.
Perhaps you can check in the same way which libgivaro gets linked when you
run sage in a way
On Wednesday, 31 May 2023 at 18:14:59 UTC-7 Luis Finotti wrote:
Here is one with your suggested change:
https://web.math.utk.edu/~finotti/misc/jl1.out
Here is one with the original version:
https://web.math.utk.edu/~finotti/misc/jl2.out
the line:
calling init: /usr/lib/x86_64-linux-gnu/libgi
Check this:
File
"/home/finotti/src/sage-10.0/src/sage/repl/ipython_kernel/__main__.py",
line 1
import sage.all
IndentationError: unexpected indent
On Thu, 1 Jun 2023 at 03:15, Luis Finotti wrote:
> Here is one with your suggested change:
> https://web.math.utk.edu/~finotti/misc/jl1.out
>
>
Here is one with your suggested change:
https://web.math.utk.edu/~finotti/misc/jl1.out
Here is one with the original version:
https://web.math.utk.edu/~finotti/misc/jl2.out
Again, thanks for your help!
On Wednesday, May 31, 2023 at 9:03:15 PM UTC-4 Isuru Fernando wrote:
> Can you upload the f
Can you upload the full log with `LD_DEBUG=libs` and jupyterlab somewhere
and post a link?
Isuru
On Wed, May 31, 2023 at 3:46 PM Luis Finotti wrote:
> Hello,
>
> Thanks for the help!
>
> On Wednesday, May 31, 2023 at 4:24:11 PM UTC-4 Isuru Fernando wrote:
>
> Try running JupyterLab in a shell w
Ah, sorry! I've fixed, but it is still not working:
[I 2023-05-31 20:13:22.480 ServerApp] Connecting to kernel
28308c3f-6fa3-4b63-91b6-cc5e1278
2d4d.
[I 2023-05-31 20:13:22.500 ServerApp] Connecting to kernel
28308c3f-6fa3-4b63-91b6-cc5e1278
2d4d.
[IPKernelApp] WARNING | Unknown message type
Following seems to indicate that there were some space before `import
sage.all`
Isuru
File
"/home/finotti/src/sage-10.0/src/sage/repl/ipython_kernel/__main__.py",
line 1
import sage.all
IndentationError: unexpected indent
On Wed, May 31, 2023 at 7:05 PM Luis Finotti wrote:
> Thanks again f
Thanks again for the help! It is really appreciated!
Unfortunately, it did not work:
[I 2023-05-31 20:01:40.186 ServerApp] Kernel started:
b7d122c3-383b-463b-b196-193ba26373aa
\0.00s - Debugger warning: It seems that frozen modules are being used,
which may
0.00s - make the debugger miss bre
Try adding
import sage.all
to the top of
/home/finotti/src/sage-10.0/src/sage/repl/ipython_kernel/__main__.py
Isuru
On Wed, May 31, 2023 at 5:23 PM Luis Finotti wrote:
>
> On Wednesday, May 31, 2023 at 6:10:42 PM UTC-4 Isuru Fernando wrote:
>
> Which givaro library is loaded when you do `e
On Wednesday, May 31, 2023 at 6:10:42 PM UTC-4 Isuru Fernando wrote:
Which givaro library is loaded when you do `export LD_DEBUG=libs` and run
sage from the command line?
I get:
1028008: find library=libgivaro.so.9 [0]; searching
1028008: search path=/home/finotti/src/sage-10.0
Which givaro library is loaded when you do `export LD_DEBUG=libs` and run
sage from the command line?
Isuru
On Wed, May 31, 2023 at 5:02 PM Luis Finotti wrote:
>
>
> On Wednesday, May 31, 2023 at 5:29:25 PM UTC-4 Isuru Fernando wrote:
>
> Does `import sage.all` in a sage shell work?
>
>
> In a
On Wednesday, May 31, 2023 at 5:29:25 PM UTC-4 Isuru Fernando wrote:
Does `import sage.all` in a sage shell work?
In a regular sage shell (from the command line, not in Jupyter Lab)? Yes,
no errors (or output).
--
You received this message because you are subscribed to the Google Groups
Does `import sage.all` in a sage shell work?
Isuru
On Wed, May 31, 2023 at 3:46 PM Luis Finotti wrote:
> Hello,
>
> Thanks for the help!
>
> On Wednesday, May 31, 2023 at 4:24:11 PM UTC-4 Isuru Fernando wrote:
>
> Try running JupyterLab in a shell with `export LD_DEBUG=libs` and import
> sage w
Hello,
Thanks for the help!
On Wednesday, May 31, 2023 at 4:24:11 PM UTC-4 Isuru Fernando wrote:
Try running JupyterLab in a shell with `export LD_DEBUG=libs` and import
sage with that jupyterlab instance.
That should tell you where givaro is loaded from.
Isuru
The output is very long, but m
Try running JupyterLab in a shell with `export LD_DEBUG=libs` and import
sage with that jupyterlab instance.
That should tell you where givaro is loaded from.
Isuru
On Wednesday, May 31, 2023 at 2:46:14 PM UTC-5 Isuru Fernando wrote:
> That's a different issue than this.
>
> Isuru
>
> On Wed, M
That's a different issue than this.
Isuru
On Wed, May 31, 2023 at 2:37 PM Jan Groenewald
wrote:
> Hi
>
> This https://groups.google.com/g/sage-support/c/egP7I9eGLuI/m/MsUUNLEUAQAJ
> suggests trying clang 14 for compiling sage or waiting for givaro compiled
> with clang 15.
>
> (or just try rebu
Hi
This https://groups.google.com/g/sage-support/c/egP7I9eGLuI/m/MsUUNLEUAQAJ
suggests trying clang 14 for compiling sage or waiting for givaro compiled
with clang 15.
(or just try rebuild the deb for givaro with clang15
https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/)
Re
This is an ABI incompatibility with clang 14 and 15 where givaro was
compiled with 14 and sage was compiled with 15.
I suggest downgrading to clang 14 or set flags like
https://github.com/conda-forge/sagelib-feedstock/blob/5542b278f642b772ae243b323c7cbc7a170a5f9a/recipe/build.sh#L21-L25
until we re
I am focusing on the Sage 9.8 issue of the missing symbol
__ZN6FFPACK8CharPolyIN6Givaro8Poly1DomINS1_7ModularIddvEENS1_5DenseERNT_7ElementERKS7_S9_mNS7_8Domain_t11Element_ptrEmRNSC_8RandIterENS_19FFPACK_CHARPOLY_TAGEm
Demangled with c++filt, the missing symbol is:
Givaro::Poly1Dom,
Givaro::D
Sorry for the late reply. Here are the details about my conda environment.
I am not exactly sure what other information is useful to debug this. I am
familiar with the linux tools, but am struggling with otool and vmmap to
figure out what is going on here and see whether I am picking up any
lib
On Tuesday, 30 May 2023 at 06:09:23 UTC-7 Luis Finotti wrote:
I looked at it, but I cannot tell if it is really the same issue, or how I
could check.
well ... it looks like the symbol that is found undefined is indeed of the
type mentioned there. So that would suggest that indeed a system giva
Thanks for the reply!
On Tuesday, May 30, 2023 at 2:21:22 AM UTC-4 Jan Groenewald wrote:
Also see
https://groups.google.com/g/sage-devel/c/xd64DrNzveM/m/EeWc6HuRAwAJ
... in case it is related.
I looked at it, but I cannot tell if it is really the same issue, or how I
could check.
I've seen th
Hi
Also see
https://groups.google.com/g/sage-devel/c/xd64DrNzveM/m/EeWc6HuRAwAJ
... in case it is related.
Regards,
Jan
On Tue, 30 May 2023 at 04:14, Luis Finotti wrote:
> Firstly, thank you very much for your help, Nils! I greatly appreciate it!
>
> On Monday, May 29, 2023 at 8:06:46 PM UT
Firstly, thank you very much for your help, Nils! I greatly appreciate it!
On Monday, May 29, 2023 at 8:06:46 PM UTC-4 Nils Bruin wrote:
On Monday, 29 May 2023 at 10:51:27 UTC-7 Luis Finotti wrote:
Any ideas on how to fix it? Is it just me, or a bug with version 10.0? I
followed the same ste
On Monday, 29 May 2023 at 10:51:27 UTC-7 Luis Finotti wrote:
Any ideas on how to fix it? Is it just me, or a bug with version 10.0? I
followed the same steps I've always followed:
https://doc.sagemath.org/html/en/installation/launching.html#setting-up-sagemath-as-a-jupyter-kernel-in-an-existin
On Monday, May 29, 2023 at 1:11:03 PM UTC-4 Nils Bruin wrote:
That looks like a linking error. Probably it's picking up a library from a
different sage install. Did you check that sage-10.0 runs fine by itself?
Did you check that sage-10.0 runs fine with its "own" notebook, using "sage
--not
On Monday, 29 May 2023 at 07:39:33 UTC-7 Luis Finotti wrote:
ImportError: /home/finotti/src/sage-10.0/src/sage/matrix/
matrix_modn_dense_float.cpython-311-x86_64-linux-gnu.so: undefined symbol:
_ZNK6Givaro7IntegercvNSt7__cxx1112basic_stringIcSt11char
_traitsIcESaIcEEEB5cxx11Ev
Any ideas on wha
config.log please
On Wednesday, May 24, 2023 at 3:16:25 PM UTC-7 Matthias Goerner wrote:
> Hi!
>
> I can't get sage to work when installing it with conda on a new MacBook
> Pro with M2 chip and Ventura 13.3.
>
> I tried
> conda -n sage create sage=9.X python=3.Y
> for (X,Y) = (5,10), (8,10), (8,
9.7 with python 3.10 seems to work on Ventura 13.3 on a M2.
On Wed, May 24, 2023 at 3:16 PM Matthias Goerner wrote:
> Hi!
>
> I can't get sage to work when installing it with conda on a new MacBook
> Pro with M2 chip and Ventura 13.3.
>
> I tried
> conda -n sage create sage=9.X python=3.Y
> for
Than you for hint. I followed instructions from page
https://sagemanifolds.obspm.fr/install_ubuntu.html and I built sage from
sources and it works. A compilation lasted several hours but at last all
works.
Best regards
Michal
ut 29. 11. 2022 o 22:14 Eric Gourgoulhon
napísal(a):
> Maybe there i
On Sat, 11 Feb 2023 at 22:11, Dima Pasechnik wrote:
>
>
> I'm just running
>>
>> make -j ptestlong
>>
>
> yes. Although -j without a parameter is a bit risky...
>
Point taken Dima about using -j without a parameter. That could have been
tricky if doctesting had used thousands of threads.😂😂
TLDR
On Sat, 11 Feb 2023 at 22:22, julian...@gmail.com
wrote:
> Hi Dave,
>
> On Saturday, February 11, 2023 at 10:33:04 PM UTC+2 David Kirkby wrote:
> (base) drkirkby@canary:~$ command -v R
> /home/drkirkby/miniforge3/bin/R
>
> something went wrong in your conda setup I believe. With the instructions
Hi Dave,
On Saturday, February 11, 2023 at 10:33:04 PM UTC+2 David Kirkby wrote:
(base) drkirkby@canary:~$ command -v R
/home/drkirkby/miniforge3/bin/R
something went wrong in your conda setup I believe. With the instructions
in the documentation, R should be installed in the sage-dev environmen
On Sat, Feb 11, 2023 at 9:59 PM Dr. David Kirkby wrote:
> On Sat, 11 Feb 2023 at 21:31, Dima Pasechnik wrote:
>
>> we have 9.8 now :-)
>> https://github.com/sagemath/sage/releases
>>
>
> Okay, I'm trying again.
>
> It seems an unusual build process.
> * There's a configure.ac, but no configure s
On Sat, 11 Feb 2023 at 21:31, Dima Pasechnik wrote:
> we have 9.8 now :-)
> https://github.com/sagemath/sage/releases
>
Okay, I'm trying again.
It seems an unusual build process.
* There's a configure.ac, but no configure script.
* I typed make, which then builds a configure script, and exits w
On Sat, Feb 11, 2023 at 9:23 PM Dr. David Kirkby wrote:
> On Sat, 11 Feb 2023 at 21:06, Dima Pasechnik wrote:
>
>> On Sat, Feb 11, 2023 at 8:33 PM David Kirkby wrote:
>>
>>> /home/drkirkby/miniforge3/bin/R
>>
>>
>> Oh, you build in Conda...
>> This might be a bit of a problem - it's not too wel
On Sat, Feb 11, 2023 at 9:23 PM Dr. David Kirkby wrote:
> On Sat, 11 Feb 2023 at 21:06, Dima Pasechnik wrote:
>
>> On Sat, Feb 11, 2023 at 8:33 PM David Kirkby wrote:
>>
>>> /home/drkirkby/miniforge3/bin/R
>>
>>
>> Oh, you build in Conda...
>> This might be a bit of a problem - it's not too wel
On Sat, 11 Feb 2023 at 21:06, Dima Pasechnik wrote:
> On Sat, Feb 11, 2023 at 8:33 PM David Kirkby wrote:
>
>> /home/drkirkby/miniforge3/bin/R
>
>
> Oh, you build in Conda...
> This might be a bit of a problem - it's not too well-tested for sure.
> Did you see https://doc.sagemath.org/html/en/in
On Sat, Feb 11, 2023 at 8:33 PM David Kirkby wrote:
> On Saturday, 11 February 2023 at 13:39:52 UTC Dima Pasechnik wrote:
> On Fri, Feb 10, 2023 at 9:10 PM David Kirkby wrote:
> It looks like sagemath_doc_html-none.is failing to build - full log of
> that package only at
>
> https://www.kirkbymi
On Fri, Feb 10, 2023 at 9:10 PM David Kirkby wrote:
> It looks like sagemath_doc_html-none.is failing to build - full log of
> that package only at
>
> https://www.kirkbymicrowave.co.uk/sagemath_doc_html-none.log
>
> This is the end of the logfile.
>
> Build finished. The built documents can be f
It looks like sagemath_doc_html-none.is failing to build - full log of that
package only at
https://www.kirkbymicrowave.co.uk/sagemath_doc_html-none.log
This is the end of the logfile.
Build finished. The built documents can be found in
/home/drkirkby/sage/local/share/doc/sage/inventory/en/r
Thank you, Matthias. I was indeed able to build sage after passing
"--without-system-singular" to "./configure". Still working on figuring out
how to merge the branch of the ticket you suggested.
Best,
Alex
On Thursday, January 5, 2023 at 10:54:13 AM UTC-8 Matthias Koeppe wrote:
> I see the fo
I see the following error in sagelib-*.log:
#define LOCAL_HIREMAINDER register ulong hiremainder
^
sage/rings/polynomial/multi_polynomial_libsingular.cpp:35068:120:
error: use of undeclared identifier 'pTakeOutComp1'; did you mean
'pTakeOutComp'?
I tried running 'make' again but am getting stuck at the same spot.
I did not pass any arguments to configure. I don't have a good idea of how
this process works so i did not deviate from the instructions in README.md
(as far as I know).
I did indeed run source .homebrew-build-env before configur
Some observations:
- It's showing a different error now.
- I find it unusual that more packages haven't been built before it tries
to build sagelib. You could try "make" again and see how far it gets.
- config.log says
Invocation command line was
$ ./configure
PKG_CONFIG_PATH=/opt/homebrew/
Hi John,
Sorry, just after I sent my previous message I realized I should have typed
'make typing_extensions' and not 'make typing_extension' so I am no longer
getting the error I indicated above. I am currently building with no errors
so far, so I will send another update soon.
Best,
Alex
On We
Maybe you also need to do "make flit_core" before "make typing_extension".
On Wednesday, January 4, 2023 at 11:35:39 AM UTC-8 John H Palmieri wrote:
> Many of the errors are discussed at https://trac.sagemath.org/ticket/34838.
> You can probably avoid those by running "make typing_extensions" be
Many of the errors are discussed at https://trac.sagemath.org/ticket/34838.
You can probably avoid those by running "make typing_extensions" before
running "make".
The most recent error seems to be for sagelib:
ld: library not found for -lopenblas
I assume that you followed the directions
Here is the problem and the solution if I am not wrong on the diagnostic :
https://stackoverflow.com/questions/70753768/jupyter-notebook-access-to-the-file-was-denied
Le 29/11/2022 à 22:14, Eric Gourgoulhon a écrit :
Maybe there is something wrong in the SageMath package for your system.
Since
Since ubuntu 22.04, there is bug in jupyter python/sage apparently not
disturbing people because i hardly found a work around. When starting
sage or jupyter we have this problem, the file is not found. I can't
remenber what the expression I put in the icon to work . I found in google.
Sorry
Maybe there is something wrong in the SageMath package for your system.
Since your system is based on Ubuntu, I would advise to build SageMath from
sources by following these lines:
https://sagemanifolds.obspm.fr/install_ubuntu.html
It's just a few lines to copy and paste in a terminal. The benef
That was the problem. I copy the files and now everything works.
Many thanks for spotting the problem.
On Saturday, 30 July 2022 at 15:25:54 UTC+2 Marc Culler wrote:
> The reason it works for one user and not for the other is because
> libgsl.25.dylib
> exists within one user's.conda/envs/sage
The reason it works for one user and not for the other is because
libgsl.25.dylib
exists within one user's.conda/envs/sage/lib directory but it does not
exist within the other user's .conda/envs/sage/lib directory.
On Saturday, July 30, 2022 at 4:53:36 AM UTC-5
domingo.domingogo...@gmail.com w
Thanks! Indeed in an update libflint-2.8.5 was updated to 2.9.0.
I've successfully rebuilt and it seems to be running fine.
On Monday, July 25, 2022 at 12:14:55 PM UTC-4 Matthias Koeppe wrote:
> From the crash report:
> ImportError: libflint-2.8.5.so: cannot open shared object file: No such
>From the crash report:
ImportError: libflint-2.8.5.so: cannot open shared object file: No such
file or directory
Likely, a system update (apt-get upgrade) removed this version of the
shared library.
Rebuild Sage from scratch.
See also https://trac.sagemath.org/ticket/34203
On Monday, July 25
Try building the latest development release of Sage,
currently Sage 9.7.beta4, instead of Sage 9.5.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+
Thank you for your answer. I installed the missing dependencies, but the
result is the same. I'll try fully cleaning the system before trying again,
perhaps some misplaced files remained.
czwartek, 7 lipca 2022 o 20:26:29 UTC+1 Matthias Koeppe napisał(a):
> This looks like https://trac.sagemath
This looks like https://trac.sagemath.org/ticket/31403
On Thursday, July 7, 2022 at 6:20:11 AM UTC-7 maksm...@gmail.com wrote:
> Hello,
>
> I'm working on Ubuntu 22.04, dual booted to Windows 10 on separate
> partition. The linux build is currently entirely fresh, after reinstalling,
> there's
Hi,
On Tue, Jun 14, 2022 at 4:30 AM Jaco Van Tonder
wrote:
> This fixes the Singular library load problem but I now have another problem.
> When I try to load the sage kernel on Jupyter Lab it can't connect:
>
> [I 2022-06-14 12:24:36.977 ServerApp] Kernel started:
> 7081cbfd-e5e1-4168-b1e4-cac
Hi Vegard,
This fixes the Singular library load problem but I now have another
problem. When I try to load the sage kernel on Jupyter Lab it can't connect:
[I 2022-06-14 12:24:36.977 ServerApp] Kernel started:
7081cbfd-e5e1-4168-b1e4-cac56170523f
/home/jacovantonder/anaconda3/bin/python3: Error
On Fri, Jun 10, 2022 at 12:50 PM 'Alan Stafford' via sage-support
wrote:
>
> sudo cd /
> sudo rm -r *.*
I don't think this is an appropriate joke to post here.
We might have to start screening your posts...
Dima
>
>
>
> On Friday, 10 June 2022, 10:41:59 BST, Vegard Lima
> wrote:
>
>
> Hi,
>
sudo cd / sudo rm -r *.*
On Friday, 10 June 2022, 10:41:59 BST, Vegard Lima
wrote:
Hi,
there should be a fix for this in updates-testing for Fedora 36:
$ sudo dnf update sagemath --enablerepo=updates-testing
You might have to do this first:
$ sudo dnf erase sagemath-doc-en
Cheers,
Hi,
there should be a fix for this in updates-testing for Fedora 36:
$ sudo dnf update sagemath --enablerepo=updates-testing
You might have to do this first:
$ sudo dnf erase sagemath-doc-en
Cheers,
Vegard
On Thu, Jun 2, 2022 at 9:36 AM Francesco Buscemi wrote:
>
> Hello there; any news? I'm g
Hello there; any news? I'm getting exactly the same errors...
On Wednesday, May 11, 2022 at 7:23:15 PM UTC+9 jacovant...@gmail.com wrote:
> I am running Fedora 36 (had the same issue in Fedora 35) on a Lenovo
> IdeaPad. After installing sage using dnf I tried running it but it failed
> due to:
Report Fedora packaging bugs to Fedora
On Wednesday, May 11, 2022 at 3:23:15 AM UTC-7 jacovant...@gmail.com wrote:
> I am running Fedora 36 (had the same issue in Fedora 35) on a Lenovo
> IdeaPad. After installing sage using dnf I tried running it but it failed
> due to: "ImportError: cannot lo
Hi,
Thank you, everyone. Sorry for my late response: I wasn't sure how things
worked and I hadn't realized that I needed to check the google groups page.
I managed to install Sage on my laptop, but I am not really sure what
worked. It was just a lot of trial and error and going through the AS
In case this problem has not been addressed ... at the bottom of your crash
report it says:
'/usr/lib/libgfortran.5.dylib' (no such file)
That means that you are using an early prelease version of the SageMath app
for M1 systems. This problem was fixed in the release version. So just
download
2022-02-16, 02:43:20 UTC, Bharathwaj Palvannan:
> I had already sent a crash report some weeks ago
> but I received no response.
This question of yours from 2017 was not answered:
https://groups.google.com/g/sage-support/c/0dgWgFGxYQU
(hopefully you managed to solve that problem since then?)
I’m in trouble:
The previous steps (make giac-clean && make fricas-clean && make
sagelib-clean && make) failed ; I reverted to (make distclean && make) …
which failed.
Repeatedly…
I’ll report and post logs in sage-release, which seems te “right place” for
an installation problem occurring o
Now, at the *end* of a Sage session, I get :
sage: quit
Exiting Sage (CPU time 0m5.63s, Wall time 97m53.10s).
/usr/local/sage-9/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/cysignals/signals.cpython-39-x86_
make giac-clean && make did it !
(*Alla cinese*) 10^4 thanks !
Le vendredi 10 décembre 2021 à 11:56:00 UTC+1, dim...@gmail.com a écrit :
> Everything that depends on updated Debian libs has to be rebuilt - looks
> like
>
> make giac-clean
>
> is needed too, for sure.
>
> On Fri, Dec 10, 2021
Everything that depends on updated Debian libs has to be rebuilt - looks like
make giac-clean
is needed too, for sure.
On Fri, Dec 10, 2021 at 10:36 AM Emmanuel Charpentier
wrote:
>
>
>
> Le vendredi 10 décembre 2021 à 01:04:33 UTC+1, Matthias Koeppe a écrit :
>>
>> "make sagelib-clean" will fi
1 - 100 of 3163 matches
Mail list logo
