-
Notifications
You must be signed in to change notification settings - Fork 951
unable to build due to sys/unix (but sys/unix not used) #425
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
Comments
The last line there is showing (non-tiny) go is able to compile and execute the wasm and get the output ('we did all the things') |
There probably still is a dependency somewhere. TinyGo won't add a random dependency for no reason. Note that we do not support Go modules yet, everything is GOPATH based (and not even $GOPATH/pkg/mod). This may confuse things. Better diagnostics are definitely a priority (goal: better diagnostics than the |
Oh... well just looking at GOPATH is probably the problem, right? Because the master branch does have the sys/unix dependency. How should I version the dependencies for tinygo? |
Versioning dependencies in TinyGo is the same as versioning dependencies in Go before Of course, we will want to support versioning eventually as it is very important. But it requires some major refactoring that is not yet completed, see #285. |
Thank you. Yeah I tried a vendor and it didn’t work.
--
Topper Bowers
[email protected]
github.com/tobowers
linkedin.com/in/topperbowers
|
Closing due to age. Thanks to everyone! |
I'm sorry I don't have an easy reproduction for this (it's a private repo and a complicated build path). However I can show it happens below.
The meat of it is that it believes one of my repos has a dependency on x/sys/unix but it doesn't (as proven by the
go mod graph | grep unix
below).The only thing I can think of is that the master branch of that repo does have a dependency on x/sys/unix . I tried to vendor everything as well, but produced the same errors.
The text was updated successfully, but these errors were encountered: