-
-
Notifications
You must be signed in to change notification settings - Fork 553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conda-forge-standard (linux): python3 spkg-configure.m4 rejects conda's python3 #31539
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
On this system, It is the |
comment:3
Moving to 9.4, as 9.3 has been released. |
comment:5
@isuruf wrote in https://groups.google.com/g/sage-devel/c/ZCjFpJGD-JA/m/5hOi6hcZBwAJ:
From the viewpoint of user installable Python packages, it is actually misconfigured, for the same reasons that led to the introduction of this check in #31132. |
comment:7
From isuruf in #31132 comment:77:
|
comment:8
A previous attempt to use Has there been a discussion in conda-forge regarding this misconfiguration of python3? |
comment:9
Nope, but the use-case we have in sage is really a rare case because we usually don't want to override a library in a conda environment. Removing -L will cause more harm than good. Something like below should give the LDSHARED to use and ldflags to append to LDFLAGS.
|
comment:10
@mkoeppe, would you be able to help with this? I don't have experience with writing |
comment:12
Not clear from the ticket description whether this is a failure to accept a correct configuration, If the former, we can just waive Conda's Python3 python through, if we knew how to distinguish it. Is https://wiki.sagemath.org/Conda up to date? |
comment:13
Replying to @dimpase:
... it should be clear from the comments above |
Outdated; we have updated the check for |
Critical for Sage 9.3 because it is a regression of platform support
CC: @isuruf @videlec @dimpase
Component: build: configure
Issue created by migration from https://trac.sagemath.org/ticket/31539
The text was updated successfully, but these errors were encountered: