search

mrtazz / checkmake

experimental linter/analyzer for Makefiles
MIT License
1.02k stars 44 forks source link

Steps to build checkmake don't work on my environment #62

Closed junaruga closed 2 years ago

junaruga commented 2 years ago

Expected behaviour

I am not really familiar with the golang. I expected the following steps to build the the checkmake works following the document. https://github.com/mrtazz/checkmake#build

go get github.com/mrtazz/checkmake
cd $GOPATH/src/github.com/mrtazz/checkmake
make

Actual behaviour

I am using Fedora 34.

$ cat /etc/fedora-release 
Fedora release 34 (Thirty Four)

$ which go
/bin/go

$ go version
go version go1.16.8 linux/amd64

The go RPM package version is like this.

$ rpm -qf /bin/go
golang-bin-1.16.8-1.fc34.x86_64
$ echo "$GOPATH"
/home/jaruga/.go

$ go get github.com/mrtazz/checkmake
go: downloading github.com/docopt/docopt-go v0.0.0-20141128170934-854c423c8108
go: downloading github.com/olekukonko/tablewriter v0.0.0-20150822215231-b9346ac189c5
go: downloading github.com/go-ini/ini v1.11.0

$ cd $GOPATH/src/github.com/mrtazz/checkmake
bash: cd: /home/jaruga/.go/src/github.com/mrtazz/checkmake: No such file or directory

It seems that the "binary" is already installed into the /home/jaruga/.go/bin/checkmake. I am not sure if this is expected behavior.

$ ls /home/jaruga/.go/bin/checkmake
/home/jaruga/.go/bin/checkmake*

Output of checkmake --version

$ which checkmake
~/.go/bin/checkmake

$ checkmake --version
checkmake  built at  by  with

Output of checkmake --debug <your makefile>

This item doesn't fit this issue, as this issue ticket is about the installation steps.

Output of make --version

$ make --version
GNU Make 4.3
Built for x86_64-redhat-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Sample Makefile to reproduce issue

(some of these things might not apply but the more you can provide the easier it will be to fix this bug. Thanks!)

This item doesn't fit this issue, as this issue ticket is about the installation steps.