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). Actually, it is not that simple. (It never is, is it?) The DEPCHECK macro for the python3 spkg has side effects which are used throughout the sage build. One of them, in the "POST" section, is to set the variable SAGE_ARCHFLAGS which is used by all of the pip spkgs. Replacing the first argument to the macro with an empty list came closer to working than commenting out the whole thing. But there were other weird things. 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 system to turn the sage/local directory into a venv which did not include pip. Something tells me that the details of how one "removes the python3 spkg" have not really been thought through at all. That is not surprising, but the devil is in the details, as they say. - Marc -- 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 discussion visit https://groups.google.com/d/msgid/sage-devel/d927b705-3531-4542-b70d-ba5571dec5dan%40googlegroups.com.
