-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
src/setup.py, src/sage/env.py (sage_include_directories): Do not add another copy of SAGE_INC, SAGE_LOCAL/lib to include dirs, library dirs #29697
Comments
Commit: |
comment:2
I don't think it is controversial at all. Is there anyone who think we are forgetting something here? New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:4
I plan to add some doctests to make sure that functions such as |
Author: Matthias Koeppe |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
Replying to @kiwifb:
No, just needs review. |
comment:8
Well, I think you have gone after the only breakage in the last commit. Unless someone can point to a corner case, it is all positive from me. |
Reviewer: François Bissey |
comment:9
Thanks! |
comment:10
I didn't realise at the time, but that will be one less line of patching for me in sage-on-gentoo. |
comment:12
This may have caused some breakage: https://groups.google.com/d/msg/sage-release/SdxKEn7CuLM/3ru84S_zAgAJ |
Changed commit from |
comment:13
... because of incorrect usage of |
comment:14
Follow-up: #31335 |
$SAGE_LOCAL/{include,lib}
are already added to the front of the search pathsCPATH
andLIBRARY_PATH
bysage-env
.We remove code that adds another copy. This removes a dependency on
SAGE_LOCAL
during the build of sagelib.The function
sage_include_directories
, apart from its use bysetup.py
, is also used bysage.misc.cython.cython
.CC: @dimpase @kiwifb @orlitzky @isuruf
Component: build
Author: Matthias Koeppe
Branch:
9a50cba
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/29697
The text was updated successfully, but these errors were encountered: