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
#10303 gives problems with sage -ba-force #10436
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
I think running sage-check-64 earlier in sage-build would fix it (if we keep #10303). Something like this patch: diff -r 3d7bb3a7774e sage-build
--- a/sage-build
+++ b/sage-build
@@ -82,6 +82,13 @@ if [ ! -d "$SAGE_ROOT/devel/sage" ]; the
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,11 +105,4 @@ if [ $DO_BUILD_ALL = 1 ]; then
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. |
comment:3
I do not see this problem on a build where SAGE64 was not set.
This was a 32-bit build on OpenSolaris 06/2009. What system was the problem noticed? Was SAGE64 set? |
comment:4
Replying to @sagetrac-drkirkby:
This was on |
Reviewer: Jeroen Demeyer |
comment:9
Ticket is irrelevant since #10303 was never merged. |
On a clean installation of Sage including #10303, I get
Apart from this error message,
sage -ba-force
seems to work.CC: @nexttime
Component: build
Keywords: SAGE64
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/10436
The text was updated successfully, but these errors were encountered: