Ticket #10436 (new defect)

Opened 3 years ago

Last modified 2 years ago

#10303 gives problems with sage -ba-force

Reported by: jdemeyer Owned by: GeorgSWeber
Priority: major Milestone: sage-5.11
Component: build Keywords: SAGE64
Cc: leif Work issues:
Report Upstream: N/A Reviewers:
Authors: Merged in:
Dependencies: Stopgaps:

Description (last modified by jdemeyer) (diff)

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

comment:1 Changed 3 years ago by jdemeyer

  • Description modified (diff)

comment:2 Changed 3 years ago by jhpalmieri

I think running sage-check-64 earlier in sage-build would fix it (if we keep #10303). Something like this patch:

  • sage-build

    diff -r 3d7bb3a7774e sage-build
    a b if [ ! -d "$SAGE_ROOT/devel/sage" ]; the 
    8282    exit 1 
    8383fi 
    8484 
     85# Check whether this seems to a 64-bit build: 
     86source "$SAGE_LOCAL"/bin/sage-check-64 
     87 
     88if [ $? -ne 0 ]; then 
     89    exit 1 
     90fi 
     91 
    8592if [ $DO_BUILD_ALL = 1 ]; then 
    8693   CUR=`pwd` 
    8794   cd "$SAGE_ROOT/devel/sage/sage" 
    if [ $DO_BUILD_ALL = 1 ]; then 
    98105   cd "$CUR" 
    99106fi 
    100107 
    101 # Check whether this seems to a 64-bit build: 
    102 source "$SAGE_LOCAL"/bin/sage-check-64 
    103  
    104 if [ $? -ne 0 ]; then 
    105     exit 1 
    106 fi 
    107  
    108108build "sage" 

But 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.

comment:3 follow-up: ↓ 4 Changed 3 years ago by drkirkby

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 in reply to: ↑ 3 Changed 3 years ago by jdemeyer

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 3 years ago by leif

  • Cc leif added

comment:6 Changed 3 years ago by jdemeyer

  • Milestone changed from sage-4.6.1 to sage-4.6.2

comment:7 Changed 2 years ago by jdemeyer

  • Priority changed from blocker to major
Note: See TracTickets for help on using tickets.