Opened 12 years ago
Closed 9 years ago
#10436 closed defect (wontfix)
#10303 gives problems with sage -ba-force
Reported by: | Jeroen Demeyer | Owned by: | Georg S. Weber |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | build | Keywords: | SAGE64 |
Cc: | Leif Leonhardy | Merged in: | |
Authors: | Reviewers: | Jeroen Demeyer | |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
On a clean installation of Sage including #10303, I get
$ ./sage -ba-force *** TOUCHING ALL CYTHON (.pyx) FILES *** KeyError: 'SAGE64': File "/mnt/usb1/scratch/jdemeyer/merger/sage-4.6.1.rc0/devel/sage-main/c_lib/SConstruct", line 108: if os.environ['SAGE64']=="yes": File "/mnt/usb1/scratch/jdemeyer/merger/sage-4.6.1.rc0/local/lib/python/UserDict.py", line 22: raise KeyError(key) ---------------------------------------------------------- sage: Building and installing modified Sage library files.
Apart from this error message, sage -ba-force
seems to work.
Change History (11)
comment:1 Changed 12 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 12 years ago by
comment:3 follow-up: 4 Changed 12 years ago by
I do not see this problem on a build where SAGE64 was not set.
drkirkby@hawk:~/sage-4.6.1.alpha3$ ./sage -ba-force *** TOUCHING ALL CYTHON (.pyx) FILES *** scons: `install' is up to date. ---------------------------------------------------------- sage: Building and installing modified Sage library files. Installing c_lib
This was a 32-bit build on OpenSolaris 06/2009.
What system was the problem noticed? Was SAGE64 set?
comment:4 Changed 12 years ago by
Replying to drkirkby:
What system was the problem noticed? Was SAGE64 set?
This was on sage.math.washington.edu
, a Ubuntu Linux x86_64 system. I did not set SAGE64
.
comment:5 Changed 12 years ago by
Cc: | Leif Leonhardy added |
---|
comment:6 Changed 12 years ago by
Milestone: | sage-4.6.1 → sage-4.6.2 |
---|
comment:7 Changed 12 years ago by
Priority: | blocker → major |
---|
comment:8 Changed 9 years ago by
Milestone: | sage-5.11 → sage-5.12 |
---|
comment:9 Changed 9 years ago by
Milestone: | sage-6.1 → sage-duplicate/invalid/wontfix |
---|---|
Reviewers: | → Jeroen Demeyer |
Status: | new → needs_review |
Ticket is irrelevant since #10303 was never merged.
comment:10 Changed 9 years ago by
Status: | needs_review → positive_review |
---|
comment:11 Changed 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | positive_review → closed |
Note: See
TracTickets for help on using
tickets.
I think running sage-check-64 earlier in sage-build would fix it (if we keep #10303). Something like this patch:
sage-build
# Check whether this seems to a 64-bit build:source "$SAGE_LOCAL"/bin/sage-check-64if [ $? -ne 0 ]; thenexit 1fiBut it's the end of the quarter here, I have final exams to prepare, etc., so I don't have any more time to work on this now.