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
18 matches
Mail list logo
