-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Sage 7.5 binaries do not build #22175
Comments
comment:1
Is this on every machine or just one? |
comment:3
Mmmm what is strange is that SAGE_FAT_BINARIES is not mentioned in Singular's spkg-install... |
comment:4
Every machine, logs are at http://build.sagedev.org/#/builders?tags=%2Bbinary-pkg |
comment:5
I don't know if this is relevant, but on my computer (Xeon E5-2623 running Ubuntu 16.04), I could build Sage 7.5 with
Here is what I did:
|
comment:6
Works as well for me on ppc64 except for #22179. |
comment:7
I think the hard-coded |
comment:9
In fact plain singular fails when installed in a long path:
|
comment:11
Upstream at Singular/Singular#811 New commits:
|
Upstream: Reported upstream. No feedback yet. |
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:14
From a fresh git clone + git pull of the ticket branch, with a long path for Sage root (252 characters), build fails with the error
As you can see from the error message above:
there seems to remain some truncation issue. |
Log of failed singular build with long path on Ubuntu 16.04 |
comment:15
Attachment: singular-4.1.0p1.log Could you also post |
config.log corresponding to the failed build of singular with long path |
comment:16
Attachment: config.log I should have been more specific. |
The config.log in SAGE_ROOT/local/var/tmp/sage/build/singular-4.1.0p1/src |
comment:17
Attachment: config.2.log That is the shebang line length exceeded and manifests itself in the "bad interpreter" error. On Linux, the shebang (line starting with #! at the beginning of a script) is limited to 127 chars. We already take that into account when building binaries. Note that the freegb.lib library path is a good bit longer than the path to the singular binary (which necessarily appears in the shebang). |
comment:18
Patch is now merged in upstream |
Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, but not in a stable release. |
Author: Volker Braun |
comment:21
Replying to @vbraun:
OK, sorry for the noise... |
comment:22
With a small path, build completed sucessfully. Since the patch has been merged upstream, I think we can set this to positive review. François, Jean-Pierre do you agree? |
Reviewer: Eric Gourgoulhon |
Sage doesn't build in long (~100 chars) directories:
Upstream: Fixed upstream, but not in a stable release.
CC: @jpflori @kiwifb
Component: build
Author: Volker Braun
Branch/Commit: u/vbraun/sage_7_5_binaries_do_not_build @
d31d416
Reviewer: Eric Gourgoulhon
Issue created by migration from https://trac.sagemath.org/ticket/22175
The text was updated successfully, but these errors were encountered: