Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 394
    • Issues 394
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2421
Closed
Open
Created May 17, 2024 by Troels Henriksen@athas

Installation woes again

I am trying to install SAC. I have downloaded the most recent snapshot packages. I encountered the following difficulties.

  • The tarball is unexpectedly a tarbomb, which was annoying to clean up after (I should probably write a script to do that).
  • The install.sh script is not executable and is not an sh script, but a bash script. I was confused when sh install.sh gave me a syntax error. The shebang is #!/usr/bin/env bash, which is correct, so this problem can be fixed by just chmodding file +x.
  • The README tells me to pass -s to install.sh, but this option is not accepted. After removing -s, it does run, but it does not install any sac2c binary.
  • I remember something about having to pass -- -S to the script to make it produce sac2c symlinks, but when doing so I get this error: /home/coancea/sac/installers/installer-debug.sh: /home/coancea/sac/sac2c-version-manager: /usr/sbin/python3.11: bad interpreter: No such file or directory. The problem here is hardcoding python3.11 specifically. (And also /usr/sbin seems like a strange location.) I changed the shebang to #!/usr/bin/env python3.
  • After this, I do have a sac2c on PATH, but running it produces this error:
$ sac2c
ERROR: library 'libsac2c_p.so' not found.
dlopen: /builds/sac-group/build-sac-pkgs/sac2c-build/sac2c-release/src/sac2c-release-build/lib/libsac2c_p.so: cannot open shared object file: No such file or directory

I think I can fiddle with the dynamic linker path to make it pick up libsac2c_p.so (which I guess is somewhere in ~/.local), but it would be nice if the installation instructions could clarify this.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking