go build works fine but go run fails

Question

I have a few files in the main package under one directory:

main.go config.go server.go

When I do: "go build" the program builds perfect and runs fine. When I do: "go run main.go" it fails.

Output:

# command-line-arguments
./main.go:7: undefined: Config
./main.go:8: undefined: Server

The symbols that are undefined are structs and they are capitalised so should be exported.

My Go version: go1.1.2 linux/amd64

What is the package for main.go and config.go with server.go? If you are going to run them all three must have package main. — Kavu
– Kavu, Commented Jan 22, 2014 at 20:19
Keep in mind that go run is fairly limited. You should be using go build to build your package(s) and running it with ./packagename or packagename if it's on your PATH. — elithrar
– elithrar, Commented Jan 22, 2014 at 21:25
You can build and execute easily without go run: "go build && ./packagename" — Matthias
– Matthias, Commented Jan 23, 2014 at 11:12

Nick Craig-Wood · Accepted Answer · 2014-01-22 20:33:07Z

67

This should work

go run main.go config.go server.go

Go run takes a file or files and it complies those and only those files which explains the missing symbols in the original post.

answered Jan 22, 2014 at 20:33

Nick Craig-Wood

54.4k13 gold badges131 silver badges138 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Roel Van Nyen Over a year ago

This indeed works but the wierd thing is that external imports (the ones you put in import()) do work perfectly without me having to specify them on the command line.

Cubic Over a year ago

@RoelVanNyen That's not weird at all - since they're imported, the go toolchain knows where to look for them

Ian Lewis Over a year ago

Would be great though if the companion packages were imported automatically by go run

Gianfranco Reppucci Over a year ago

@RoelVanNyen Why didn't you suggest go run *.go?

cody Over a year ago

There is a side effect for me: $ go run *.go go run: cannot run *_test.go files (main_test.go) There's a discussion around this here

|

Daniel Pecos · Accepted Answer · 2018-10-09 12:29:00Z

44

You could execute it as:

go run .

so you don't have to include all files manually.

answered Oct 9, 2018 at 12:29

Daniel Pecos

5815 silver badges5 bronze badges

Comments

Piyush Bag · Accepted Answer · 2022-05-06 15:23:33Z

3

Good practise would be to create a package for it and run

go run ./app

Ex. Folder Structure

    ├──app/
    |  ├──main.go
    |  ├──config.go
    |  ├──server.go
    ├──bin/
    |  ├──foo.go
    └──pkg/
       └──bar.go

answered May 6, 2022 at 15:23

Piyush Bag

1012 silver badges11 bronze badges

Collectives™ on Stack Overflow

go build works fine but go run fails

3 Answers 3

6 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

6 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related