singularity icon indicating copy to clipboard operation
singularity copied to clipboard

error installing singularity

Open karthickbrlab opened this issue 1 year ago • 3 comments

Hi kindly help me to sort this out make -C builddir make: Entering directory '/home/ubuntu/go/src/github.com/sylabs/singularity-3.8.7/builddir' /bin/sh: 1: /home/ubuntu/go/src/github.com/sylabs/singularity-3.8.7/scripts/go-generate: Permission denied make: *** [Makefile:165: /home/ubuntu/go/src/github.com/sylabs/singularity-3.8.7/internal/pkg/buildcfg/config.go] Error 126 make: Leaving directory '/home/ubuntu/go/src/github.com/sylabs/singularity-3.8.7/builddir'

karthickbrlab avatar Apr 10 '24 10:04 karthickbrlab

Hi @karthickbrlab, please follow the instructions in https://github.com/sylabs/singularity/blob/main/INSTALL.md if you wish to install from source. Also note that Singularity 3.8.7 is very old, I would recommend updating to the latest release (https://github.com/sylabs/singularity/releases). Depending on the version of Ubuntu you are running, a pre-built .deb may also be available in the releases section.

tri-adam avatar Apr 10 '24 14:04 tri-adam

Hi My ubuntu version is Ubuntu 22.04.3 LTS - jammy. I have installed the newer version of singularity 4.1.2..but im unable to configure, as host go compiler not found. although i have tried 1.21.8 as well as the recent go version 1.22.2.

$ go version go version go1.22.2 linux/amd64

./mconfig Configuring for project `singularity-ce' with languages: C, Golang => running pre-basechecks project specific checks ... => running base system checks ... checking: host C compiler... cc checking: host C++ compiler... c++ checking: host Go compiler (at least version 1.20)... not found! mconfig: could not complete configuration

IS THERE ANY VERSION SPECIFICITY?

karthickbrlab avatar Apr 11 '24 06:04 karthickbrlab

OK, that looks like a problem with your Go installation. The command that is run by config to check for the Go compiler is:

$ go run mlocal/checks/version.go go1.20
Found Go release tag go1.20.

Running that might shed some light on why the check is failing.

The most common thing that causes that check to fail is having upgraded Go over a previous installation rather than removing the old installation first. It might be worth re-installing Go following the instructions at https://go.dev/doc/install to rule that out.

tri-adam avatar Apr 12 '24 14:04 tri-adam

Closing as there hasn't been any follow-up. If the issue isn't resolved, please feel free to re-open this with some additional information about how exactly you installed Go.

dtrudg avatar Jun 14 '24 09:06 dtrudg