I wanted to run a test of one of my go apps. This is, what the output said:

# runtime/cgo
cgo: exec x86_64-solus-linux-gcc: exec: "x86_64-solus-linux-gcc": executable file not found in $PATH

I'm sure someone knows how to quickly solve this. 😬
Or is it just to put that fielpath into $PATH ?
What is that solus file?

Normal build runs just fine.

Okay...
sudo eopkg install -c system.devel
solved the problem.
Didn't ever have to do this on other distros 🤷‍♂️

@DasJott sounds like you accidentally ran go test for all of Go, not just the current project. We are now on Go 1.16 which requires Go modules by default, which may be related. But you should no longer be modifying GOPATH directly. Go modules are much much nicer to deal with.

6 days later

I know. I work with go a lot. Made many microservices and other stuff with it for the company I work for.
I also know go mod.

Problem here was indeed that it couldn't run a particular test I wanted to run. Didn't know build tools were needed for that, because the usual build ran fine.
I guess on Manjaro it was already installed because of their AUR stuff...

    DasJott Sorry, wasn't sure if you were trying to do it on purpose or not. It's an easy thing to do by accident. Yeah, we don't bundle build tools because (in theory) most people don't need them.

      Everything cool! 🙂
      How could anybody know 🤷‍♂️ 😁
      Was just wondering why the normal build would work, but the test not... but in the end it doesn't matter.

      Still have a Manjaro working on my private machine for coding but thinking of moving to Solus Budgie there as well. I love the simplicity a lot!

      @DasJott Never tried Manjaro, but I use Solus for my work which is for the most part also coding. Although I use Solus Plasma for work and Budgie for fun stuff.