-
-
Notifications
You must be signed in to change notification settings - Fork 535
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
Move local/bin/sage-check-64 to spkg/bin/sage-arch-env #12789
Comments
This comment has been minimized.
This comment has been minimized.
Author: Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:8
Replying to @jhpalmieri:
Too bad those tickets got abandoned, as they are bitrotten now. Anyway, I will look at those tickets and take the good ideas here. |
This comment has been minimized.
This comment has been minimized.
comment:10
Added items 5 and 6. One idea from #10303 that I disagree with is to source |
comment:11
Replying to @jdemeyer:
Well, Cython should take Doesn't really make sense to change the settings ( |
comment:12
Shouldn't there be at least a warning if Since this is exactly what we want to avoid: Mixing up both. |
comment:13
Replying to @nexttime:
I believe in the philosophy of "user is always right". If the user intentionally set |
comment:14
Replying to @nexttime:
Perhaps, but I think it's not impossible that some Sage library code or user code wants to look at |
This comment has been minimized.
This comment has been minimized.
Attachment: 12789_scripts.patch.gz |
Changed keywords from none to sd40.5 |
comment:16
Attachment: 12789_root.patch.gz Looks good! |
Reviewer: Volker Braun |
Merged: sage-5.1.beta4 |
Since
sage-env
sources$SAGE_LOCAL/bin/sage-check-64
, it makes sense to move the latter file to$SAGE_ROOT/spkg/bin
. I also propose to rename the file to "sage-arch-env". I would like to support a SAGE32 flag (see #12726) and it makes sense to use the same file for this.Further changes:
$SAGE_LOCAL/etc/sage-64.txt
as indicator file forSAGE64
instead of$SAGE_LOCAL/lib/sage-64.txt
(sage-64.txt
looks more like a configuration file than a library).sage-check-64
(they were being redirected to /dev/null anyway).SAGE64
or other future architecture flags.sage-check-64
fromlocal/bin/sage-build
. The latter script is only called fromspkg/bin/sage
at which pointSAGE64
is already set if needed.SAGE64
is supported on all systems of course).Apply:
Component: scripts
Keywords: sd40.5
Author: Jeroen Demeyer
Reviewer: Volker Braun
Merged: sage-5.1.beta4
Issue created by migration from https://trac.sagemath.org/ticket/12789
The text was updated successfully, but these errors were encountered: