#5628: [with patch; needs review] a little sage-flags.txt issue
--------------------------+-------------------------------------------------
Reporter: was | Owner: was
Type: defect | Status: new
Priority: blocker | Milestone: sage-3.4.1
Component: distribution | Keywords:
--------------------------+-------------------------------------------------
Comment(by tornaria):
I have an alternative fix:
{{{
diff -r 804879ae0134 sage-location
--- a/sage-location Thu Mar 26 16:43:48 2009 -0700
+++ b/sage-location Sat Mar 28 22:32:50 2009 -0700
@@ -77,7 +77,7 @@
if not os.path.exists(flags_file): return
# We check that the processor flags of the original build are a
# subset of the new machine. If not, we print a massive warning.
- X = set(open(flags_file).read().split())
+ X = set(open(flags_file).read().split()).intersection(FLAGS)
Y = set(get_flags_info().split())
if not X.issubset(Y):
print ""
}}}
This makes it so that only the flags listed in FLAGS are relevant for
{{{check_processor_flags()}}}. Thus, after an upgrade, the flag
{{{sse4_1}}} will still be in the flags file, but it won't be required at
runtime.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5628#comment:3>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
