Skip to content

gopherjs serve results in go/1.6.2/libexec/src/runtime/error.go:58:7: undeclared name: efaceOf #459

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.

Sign up for GitHub

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

Jump to bottom
Closed
gorakhargosh opened this issue May 12, 2016 · 4 comments
Closed

gopherjs serve results in go/1.6.2/libexec/src/runtime/error.go:58:7: undeclared name: efaceOf #459

gorakhargosh opened this issue May 12, 2016 · 4 comments

Comments

@gorakhargosh
Copy link

Namaste,

 [130]fish> gopherjs serve -w foo
serving at http://localhost:8080 and on port 8080 of any available addresses
../../../../usr/local/Cellar/go/1.6.2/libexec/src/runtime/error.go:58:7: undeclared name: efaceOf

fish> tree
m.
└── src
    └── foo
        └── script.go

Sending a GET request to localhost:8080/foo/ results in the above error.

How does one get gopherjs serve to work?
@bep
Copy link

bep commented May 12, 2016

Not sure what the foo is all about, but the root is the "package root" of your gopherjs package(s).

So, to give an example from a repo of mine.

gopherjs serve github.com/bep/gr/examples

If you do

gopherjs serve

You "serve" the entire gopath ...

@gorakhargosh
Copy link
Author

This is what I get when I run your example:

~/burrow
fish> gopherjs serve github.com/bep/gr/examples
serving at http://localhost:8080 and on port 8080 of any available addresses
../../../usr/local/Cellar/go/1.6.2/libexec/src/runtime/error.go:58:7: undeclared name: efaceOf

fish> echo $GOPATH
/Users/yesudeep/burrow

@dmitshur
Copy link
Member

Take a look at #434, it mentions problems with efaceOf.

I think this is unrelated to gopherjs serve, but rather to your setup of gopherjs in general. If you try to do gopherjs build with those examples, do you get the same error?

This was referenced May 12, 2016
Closed
Closed
@gorakhargosh
Copy link
Author

Nope. not the same error. for some odd reason, it's working now. closing this bug.

thank you! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gorakhargosh @bep @dmitshur