`gopherjs install -m log` outputs nothing with specifying GOROOT
Open
Nobody has claimed this yet.
bug
NeedsInvestigation
- Dominant language
- Go
- Stars
- 13.2k
- Forks
- 573
- PR merge metrics
- No merged PRs in 30d
Description
- Create
/tmp/foo - Run
GOPATH=/tmp/foo go get github.com/gopherjs/gopherjs - Copy
$GOROOT/src/**/*.goto/tmp/foo/src(**means all recursive directories) - Run
GOROOT=/tmp/foo /tmp/foo/bin/gopherjs install -m log - See
/tmp/foo/pkgand find nothing is generated.
Interestingly, some packages like image/png worked, but some packages like log and runtime didn't.
CC @j7b
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the listed GOPATH, GOROOT, and gopherjs install -m log commands, then compare the generated package results for image/png, log, and runtime. Trace the install path that decides which packages to compile; done means expected packages are generated under /tmp/foo/pkg when GOROOT points to the copied source tree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100