NVIDIA / NVIDIA/nvkind

Unable to use make to install, had to use make build instead

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
211
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Trying to install on Archlinux following steps in README:

➜  nvkind git:(main) make
go mod tidy
go mod vendor
internal error: failed to find embedded files of github.com/Masterminds/sprig/v3: /home/samos/go/pkg/mod/github.com/!masterminds/sprig/v3@v3.2.3/crypto.go:1:1: expected 'package', found 'EOF'
make: *** [Makefile:21: vendor] Error 1
➜  nvkind git:(main) ✗ git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   go.mod
        modified:   go.sum
        deleted:    vendor/github.com/Masterminds/goutils/.travis.yml
        deleted:    vendor/github.com/Masterminds/goutils/CHANGELOG.md
        deleted:    vendor/github.com/Masterminds/goutils/LICENSE.txt
        deleted:    vendor/github.com/Masterminds/goutils/README.md
        deleted:    vendor/github.com/Masterminds/goutils/appveyor.yml
        deleted:    vendor/github.com/Masterminds/goutils/cryptorandomstringutils.go
        deleted:    vendor/github.com/Masterminds/goutils/randomstringutils.go
        deleted:    vendor/github.com/Masterminds/goutils/stringutils.go
        deleted:    vendor/github.com/Masterminds/goutils/wordutils.go

However if I run make build directly it all just works fine.

make build
./nvkind -h
NAME:
   nvkind - kind for use with NVIDIA GPUs

Leaving this as feedback in case others hit the same issue.

Thanks for making this process of using GPU with kind so much easier!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the installation steps in README and the vendor target at Makefile:21. Compare the commands run by make with the make build path to identify why vendor generation fails while the build succeeds. Done means the README workflow completes successfully with make without the reported dependency or vendor errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.