Yes, that's what I'm currently trying to do, but finding all the packages
with wrong checksums is turning out to not be so fun. Have to keep
rerunning `make` to try and see which package breaks next.
2 questions though:
1. Is there not currently a way to do a "check integrity" run or something?
Wh
If I am not wrong this is caused because sometimes downloading files fail.
In my experience a direct download of the files, copied in the folder
upstream, and restarting make is enough.
El miércoles, 23 de abril de 2025 a las 19:17:15 UTC+2,
aram.derme...@gmail.com escribió:
> This definitely
On Wednesday, April 23, 2025 at 2:35:48 PM UTC-5 Dima wrote:
I haven't built any Python dependencies (unless testing stuff) for years,
and I suppose this applies to the vast majority of people doing Sage
development or installation from source.
Why do you need to build them?
Can you start with a
This definitely solves the sci-py problem! Thanks.
I'm still getting hung up on the 2nd issue though where for some reason
matplotlib just won't install. The terminal goes to something like:
```
[sagenb_export-3.3] [spkg-pipinst] Installing collected packages:
sagenb_export
[sagenb_export-3.3] [sp
On Wed, Apr 23, 2025 at 11:07 AM Marc Culler wrote:
> The venv directory gets named with the version of python used by the
> python3 spkg, even if the provided "system python" has a different
> version. Using --with-sage-venv=no seemed to avoid that quirk, but somehow
> caused the sage build sy
On Wed, Apr 23, 2025 at 11:07 AM Marc Culler wrote:
>
>
> On Monday, April 21, 2025 at 9:12:01 AM UTC-5 Michael Orlitzky wrote:
>
> IIRC you are building everything (except python, now) from SPKGs. If
> so and if you are sure that your newly-built python was linked against
> the sage copies of bz
On Monday, April 21, 2025 at 9:12:01 AM UTC-5 Michael Orlitzky wrote:
IIRC you are building everything (except python, now) from SPKGs. If
so and if you are sure that your newly-built python was linked against
the sage copies of bzip2, zlib, etc., you can just ignore the DEPCHECK
(edit it out
Hi,
This line in the scipy log:
[spkg-install] g++: fatal error: Killed signal terminated program cc1plus
points towards a memory issue. Could you increase the RAM devoted to WSL2
or decrease the number of processes if you are performing a parallel build
(e.g use make -j4 instead of make -j8) ?
