#10303 gives problems with sage -ba-force

[Jeroen Demeyer]

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.

[John Palmieri]

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

sage-build

@@ -82 +82 @@
     exit 1
 fi
 
+# Check whether this seems to a 64-bit build:
+source "$SAGE_LOCAL"/bin/sage-check-64
+
+if [ $? -ne 0 ]; then
+    exit 1
+fi
+
 if [ $DO_BUILD_ALL = 1 ]; then
    CUR=`pwd`
    cd "$SAGE_ROOT/devel/sage/sage"
@@ -98 +105 @@
    cd "$CUR"
 fi
 
-# Check whether this seems to a 64-bit build:
-source "$SAGE_LOCAL"/bin/sage-check-64
-
-if [ $? -ne 0 ]; then
-    exit 1
-fi
-
 build "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.

[David Kirkby]

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?

[Jeroen Demeyer]

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.

[Jeroen Demeyer]

Ticket is irrelevant since #10303 was never merged.