Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Error creating runtime binarys with bdist-sage-linux #11

Open
millermj1 opened this issue Jun 22, 2017 · 5 comments
Open

Error creating runtime binarys with bdist-sage-linux #11

millermj1 opened this issue Jun 22, 2017 · 5 comments

Comments

@millermj1
Copy link

If I clone https://github.com/sagemath/binary-pkg.git, edit sage.yaml to change the branch from develop to master, and run:

  • $ export PACKAGE="Runtime binaries only"
  • $ make bdist-sage-linux

then I get the errors:

  • make stage-sage
  • make[2]: Entering directory '/home/mike/Downloads/binary-pkg'
    .../binary-pkg/activate python -m binary_pkg.cmdline --config sage.yaml --stage --package "Runtime binaries only"
  • Namespace(build=False, checkout=False, config='sage.yaml', debug=False, dist=False, info=False, log=None, option_help=False, package='Runtime binaries only', stage=True)
  • WARNING:root:Suspicious text terminators [b':'] in .../binary-pkg/source/SageMath/.../local/bin/gp-2.9
  • WARNING:root:Contains zero-terminated strings but marker is not: .../binary-pkg/source/SageMath/.../local/bin/gp-2.9
  • ERROR:root:At b'.../binary-pkg/source/SageMath/.../local/share/doc/sage/html/en/reference/calculus/sage/calculus/ode.htmlX\x1e'
  • ERROR:root:path terminator b'\x1e' not allowed in .../binary-pkg/source/SageMath/.../local/share/doc/sage/doctrees/ca/intro/environment.pickle
  • invalid string terminator
  • Makefile:19: recipe for target 'stage-sage' failed
  • make[2]: *** [stage-sage] Error 1

All the files in the directory .../binary-pkg/source/SageMath/.../local/share/doc/sage/html/en/reference/calculus/sage/calculus end in html .

Without the "export package" line, the compile succeeds, but I want to shrink the size as much as possible.

Thanks!

@vbraun
Copy link
Member

vbraun commented Jun 22, 2017

Yes the runtime binary part isn't used regularly. The exclude: lines in sage.yaml need to be merged, anything at " Full binary tarball" needs to be added to "Runtime binaries only" if its not there already.
PR would be welcome..

@millermj1
Copy link
Author

millermj1 commented Jun 22, 2017 via email

@vbraun
Copy link
Member

vbraun commented Jun 22, 2017

Thats just YAML syntax, the rewrite_path is assigned (&) to the REWRITE_PATH_DEFAULT variable and referenced (*) later.

Only the files: section of "Runtime binaries only" needs updating....

@millermj1
Copy link
Author

millermj1 commented Jun 22, 2017 via email

@vbraun
Copy link
Member

vbraun commented Jun 23, 2017

No, the rewrite_path is correct as it stands. Only the files: section of "Runtime binaries only" needs updating....

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants