the ipython builder insists that the ipython log file must be included so
the information about a dependency can get back to the developers.
so it is attached to this reply
On Friday, February 2, 2024 at 7:43:44 PM UTC-8 Randall Rathbun wrote:
> I believe you are correct, thanks.
>
>
>
> On Friday, February 2, 2024 at 5:50:49 PM UTC-8 Randall Rathbun wrote:
>
>> Matthias
>>
>> Thanks for all your help. Even after I used yast2 to remove meson, it
>> still did NOT remove meson from my ~ .local/bin location and I had to
>> manually remove this
believing
that the files were removed.
Randall
--
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.
To view this dis
ner/.local/bin from
> PATH and re-run "configure", or alternatively use "./configure
> --without-system-meson".
>
>
> On Friday, February 2, 2024 at 4:45:31 PM UTC-8 Randall Rathbun wrote:
>
>> Here are some log and config files and my record of w
I have been able to successfully build 77 packages (of the 196 slated to be
built for sage 10.2) but now encountered a strange error with meson_python.
I went to the appropriate directory, opened up a subshell and tried to
rebuild the package.
owner@localhost:~/math/sage-10.2/local/var/lib/sage
Thank you very much for that sharp-eyed catch. The /usr/bin/python was
indeed symlinked to ipython.
I did update the CC and CXX flags also to point to version 13 which is
installed on my system.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
Thank you for the information, I will look into this. Usually yast2 gets
things right, but apparently this one failed.
--
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
Dima:
I did find a post in the openSuse group which said to update the CC and CXX
flags location to the correct versions and that was picked up correctly by
the sage build script. Matthias nailed the problem, it was with python3,
but I had to work the version a bit as openSuse Leap 15.5 adamantl
ge/sage-9.5'
-
Okay, but I would expect and I need to see any warnings in the C++ compile,
so how is exposure given to these warnings and messages during that
compile? During a main build taking several hours, during the cynthonizing
phase, many lines of compiler warn
ound looking for the cython documents and see how this
translator works.
What I see happening in my 105 cpp files is variables NOT being initialized
correctly. But this change has to come from the cythonizer, not by changing
the cpp code itself.
Randall
--
You received this message bec
ll start with the 9.4 version and build it first, then change to the
9.5 version (carefully redirecting the SAGE_ROOT and SAGE_LOCAL variables
accordingly)
- Randall
On Thursday, January 20, 2022 at 4:10:42 PM UTC-8 wst...@gmail.com wrote:
> Follow the steps in the README, e.g., here
&g
ings are failing to build.
But I am determined to carefully document ALL of this rather than answer
just off the top of my head.
So do I need to run the following steps???
1. run "m4 configure.ac"
2. run "configure"
3. run "make"
Thanks for responding..
- R
#x27;SageMath version 9.5.rc3, Release Date: 2022-01-18'
diff --git a/src/sage/version.py b/src/sage/version.py
index 80194b4f91..62d1a1b670 100644
--- a/src/sage/version.py
+++ b/src/sage/version.py
@@ -1,5 +1,5 @@
# Sage version information for Python scripts
# This file is auto-genera
changes back up into the cython code and see if they take.
On Thursday, January 20, 2022 at 2:07:06 PM UTC-8 Randall wrote:
> Thanks for all the posts, I think I am tracking. But I discovered a bad
> problem, on the original "git clone" command my download has file
> corrupt
Thanks for all the posts, I think I am tracking. But I discovered a bad
problem, on the original "git clone" command my download has file
corruption errors and some of the files are truncated. We used to deal with
this, by md5sums or sha256 sums on files and folders, so we could make sure
of bi
pointers on how to
set this up. I already have git cloned the image and have a trac account.
Randall
--
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
,
unfortunately hammering the drives and inserting disk cluster errors or
inode problems into the disk files and inodes.
On Friday, December 17, 2021 at 7:23:45 PM UTC-8 Matthias Koeppe wrote:
> On Friday, December 17, 2021 at 2:33:55 PM UTC-8 Randall wrote:
>
>> I am building sage version 9.4
William:
Personal email is on the way to you.
Randall
On Friday, December 17, 2021 at 5:49:34 PM UTC-8 wst...@gmail.com wrote:
> On Fri, Dec 17, 2021 at 2:33 PM Randall wrote:
> >
> > Hi all:
> >
> > I am building sage version 9.4 from source on my OpenSuse Linux L
nks for reading this post.
- Randall
--
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.
To view this discussio
then
installed, before attempting to do the actual Sage x.y install. I realize
that this is a big task, but surely looking through all the build logs
might give some idea of what external libraries are needed.
- Randall
--
You received this message because you are subscribed to the Google
I downloaded the generic Singular package version 3.1.1.4 from the
Singular website and attempted to compile it.
The make ran into a severe gcc-4.6 internal compiler error, so there
is apparently a bug in the gcc version 4.6 compiler.
I am going to assume (with good reason) that the gcc 4.6 compi
was forced to compile that library in single proc mode
to get it successfully to build and then build the subsequent packages
depending upon it.
I would appreciate any comments on how to fix the Singular build
problem, or how to bypass it and continue on with the few remaining
packages, so that I
22 matches
Mail list logo
