-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
configure: Paths within $SAGE_LOCAL ($prefix) for sage_conf #31593
Comments
Commit: |
comment:2
Here's a basic solution (without a new macro) that is perhaps already good enough for the moment. It is modeled after autotools' treatment of paths derived from ${prefix} such as In New commits:
|
comment:3
... which would be processed in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
comment:7
I've rebased #29617 onto this to see how it goes, but the idea looks good. Thanks! |
Reviewer: Michael Orlitzky |
comment:8
I'm optimistic, thanks again. |
comment:9
Thanks for the review! |
comment:10
Merge conflict |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
easy merge, back to positive |
Changed branch from u/mkoeppe/configure__paths_within__sage_local___prefix__for_sage_conf to |
A solution for an issue encountered in #29617
CC: @orlitzky
Component: build: configure
Author: Matthias Koeppe
Branch/Commit:
2078fa6
Reviewer: Michael Orlitzky
Issue created by migration from https://trac.sagemath.org/ticket/31593
The text was updated successfully, but these errors were encountered: