Skip to content
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

Build error: encoding/binary.decodeFast: 1456+8 not in [0,1024) #3458

Open
siegLoesch opened this issue Jan 9, 2025 · 4 comments
Open

Build error: encoding/binary.decodeFast: 1456+8 not in [0,1024) #3458

siegLoesch opened this issue Jan 9, 2025 · 4 comments

Comments

@siegLoesch
Copy link

Before you report an issue...

  • [ done] Have you searched for a duplicate report?
  • [ done] Have you replicated the problem on the latest release?
  • [ done] Have you checked the latest documentation?
  • [ done] Are you using an up-to-date system?

Version of singularity: 4.2.2

Describe the bug
Current build on debian bookworm yields the following error:

GO singularity
    [+] GO_TAGS "sylog singularity_engine fakeroot_engine apparmor selinux seccomp"
# github.com/sylabs/singularity/v4/cmd/singularity
encoding/binary.decodeFast.jump6: invalid relocation encoding/binary.decodeFast: 1456+8 not in [0,1024)
make: *** [Makefile:181: singularity] Error 1

To Reproduce

Steps to reproduce the behavior:
Carrying out install steps according file: Install.md from github or documentation in chapter: Installing SingularityCE

Expected behavior
Build without error as with version tag 4.2.1

A clear and concise description of what you expected to happen.

OS / Linux Distribution
Up to date Debian bookworm

$ cat /etc/os-release:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Installation Method
Compiled from source.

Additional context

checking: cryptsetup... yes (/sbin/cryptsetup)
 checking: go... yes (/opt/go/bin/go)
 checking: ldconfig... yes (/sbin/ldconfig)
 checking: mksquashfs... yes (/usr/bin/mksquashfs)
 checking: nvidia-container-cli... no
 checking: unsquashfs... yes (/usr/bin/unsquashfs)

=> generating fragments ...
=> building Makefile ...
=> generating singularity-ce.spec ...
=> project singularity-ce setup with :
    - host arch: x86_64
    - host wordsize: 64-bit
    - host C compiler: cc
    - host Go compiler: /opt/go/bin/go
    - host system: unix
      ---
    - target arch: x86_64
    - target wordsize: 64-bit
    - target C compiler: cc
      ---
    - config profile: release
      ---
    - SUID install: yes
    - Network plugins: yes
    - seccomp support: yes
    - Build conmon: yes
    - Build squashfuse: yes
      ---
    - verbose: no
      ---
    - cryptsetup: /sbin/cryptsetup
      ---
    - version: 4.2.2
@siegLoesch siegLoesch added the bug Something isn't working label Jan 9, 2025
@dtrudg
Copy link
Member

dtrudg commented Jan 9, 2025

What version of Go is this? If it is not the latest version, please try the latest verision from https://go.dev/doc/install

The error is being raised by Go standard library code. It is unlikely to be directly related to something in Singularity itself, and we haven't observed it on any of the platforms will build on, when using Go 1.23.4

AlmaLinux / CentOS Stream 8 / 9 / 10
Ubuntu 20.04 / 22.04 / 24.04
SLES 12 / 15

@dtrudg dtrudg added needs more info and removed bug Something isn't working labels Jan 9, 2025
@siegLoesch
Copy link
Author

I am using latest go:

go version
go version go1.23.4 linux/amd64

I'll try to reinstall go meanwhile.
Thank you for your answer!

@siegLoesch
Copy link
Author

Just did a complete fresh build of go with also removing any user bin an pkg files. he result is boring because it yields the same error as mentioned above.

@dtrudg
Copy link
Member

dtrudg commented Jan 10, 2025

Okay - I'm afraid that Debian isn't a distribution we directly test on ourselves. We can try and look into it as time allows, but it is unlikely to be a high priority at this point.

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

No branches or pull requests

2 participants