2022-01-21 à 22:33:08 UTC, Randall on sage-devel:
> I am carefully following the steps at
>
https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source
> but 2 things already have come up.
>
> The latest download version on the tar ball page
> is version 9.4 sage.
I am carefully following the steps on the
https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source
webpage
but 2 things already have come up.
The latest download version on the tar ball page is version 9.4 sage.
The latest git clone version is 9.5 rc3, but the i
Follow the steps in the README, e.g., here
https://github.com/sagemath/sage/blob/develop/README.md#instructions-to-build-from-source
None of those steps involve explicitly running m4, so I'm guessing you're
not following them.
On Thu, Jan 20, 2022 at 4:04 PM Randall wrote:
>
> I erased everythi
I erased everything and started all over again and this time carefully
logged each step.
owner@localhost:~/sage> cat step_1_logged.txt step_2_logged.txt
step_3_logged.txt step_4_logged.txt step_5_logged.txt [my log files]
owner@localhost:~> git clone https://github.com/sagemath/sage.git
Cloni
Well, since I am new at this... can anyone answer my questions?
To start, I tried to force a hard rewrite of ALL the code in my branch,
which which came from the develop branch.
This is to protect any mistakes being made.
I did a hard reset and deleted any intermediate files, using 2 git command
On Thu, Jan 20, 2022 at 2:07 PM 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 corruption
> errors and some of the files are truncated. We used to deal with this, by
> md5sums or sha2
I had to fix 110 files to fix the 371 warnings, but there are 3 legitimate
warnings, 2 appear to be missing code in the cython file. One warning is
legitimate, but it is a chicken versus egg argument, I can explain in
detail in case anyone wants to know. Now all I have to do is push all these
c
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
On Mon, 2022-01-17 at 18:35 -0800, Matthias Koeppe wrote:
> On Monday, January 17, 2022 at 5:14:30 PM UTC-8 Michael Orlitzky wrote:
>
> > Dark magic is relative, but for someone new [...]
> >
>
> (rant deleted)
>
> 1) "make build" just works
> 2) "./sage -b" just works.
>
It wasn't a rant, th
Wow that is soo awesome. Thanks Tobias!!
On Mon, Jan 17, 2022 at 6:38 PM Matthias Koeppe
wrote:
> On Monday, January 17, 2022 at 5:31:24 PM UTC-8 wst...@gmail.com wrote:
>
>> Unfortunately, the
>> "python setup.py develop" workflow didn't even exist when we first
>> made "sage -b". [...]
On Monday, January 17, 2022 at 5:31:24 PM UTC-8 wst...@gmail.com wrote:
> Unfortunately, the
> "python setup.py develop" workflow didn't even exist when we first
> made "sage -b". [...]
>
It exists now, it is called "pip install --editable" these days.
In the Sage distribution, you activate i
On Monday, January 17, 2022 at 5:14:30 PM UTC-8 Michael Orlitzky wrote:
> Dark magic is relative, but for someone new [...]
>
(rant deleted)
1) "make build" just works
2) "./sage -b" just works.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" grou
On Mon, Jan 17, 2022 at 5:14 PM Michael Orlitzky
wrote:
> On Mon, 2022-01-17 at 17:02 -0800, William Stein wrote:
> >
> >
> > When I wrote this, the steps were:
> >
> > (1) build sage
> > (2) edit the pyx/pxd file you want to change, or really anything in
> > SAGE_ROOT/src/sage
> > (3) type "sage
On Mon, 2022-01-17 at 17:02 -0800, William Stein wrote:
>
>
> When I wrote this, the steps were:
>
> (1) build sage
> (2) edit the pyx/pxd file you want to change, or really anything in
> SAGE_ROOT/src/sage
> (3) type "sage -br" to build any changes and start sage.
>
> Doing "sage -br" should h
On Mon, Jan 17, 2022 at 4:43 PM Michael Orlitzky
wrote:
> On Mon, 2022-01-17 at 15:27 -0800, Randall wrote:
> > I would like to find some developer who is willing to show me how to set
> up
> > the cythonizing part of the compile for the Sage build. I did fix 371
> > warnings in 110 code units, b
On Mon, 2022-01-17 at 15:27 -0800, Randall wrote:
> I would like to find some developer who is willing to show me how to set up
> the cythonizing part of the compile for the Sage build. I did fix 371
> warnings in 110 code units, but have to push these changes back up into the
> cython code.
I
I would like to find some developer who is willing to show me how to set up
the cythonizing part of the compile for the Sage build. I did fix 371
warnings in 110 code units, but have to push these changes back up into the
cython code.
Please contact me if you are willing to give me a few poin
17 matches
Mail list logo
