CODEWITHSUNDEEP
google-app-enginego
OldCurmudgeon
OldCurmudgeon

Reputation: 65869

Updated GAE to 1.8.6 - what do I do now

My installation of GAE told me I should upgrade.

I downloaded the zip - renamed the old folder called *go_appengine* to *go_appengine-1.8.5* and extracted a brand new *go_appengine* folder from the zip.

Now when I try to build under LiteIde I get the massage:

go build runtime: windows/386 must be bootstrapped using make.bash

and when I try to run my app I get:

Failed to build Go application: C:\Go\GAE\go_appengine\google\src\...go can't find import: "math/big"

I am sure there is a simple command I need to execute to build everything but I cannot seem to find it anywhere.

Upvotes: 3

Views: 321

Answers (3)

Dave W. Smith
Dave W. Smith

Reputation: 24966

We are aware of the problem (our goof, basically), and are in the process of building a new Go SDK for Windows.

Updated: If you're on Windows, you'll want to replace the 1.8.6 SDK with 1.8.6.1. It's up on the download site now.

Upvotes: 7

Vladimir Suhov
Vladimir Suhov

Reputation: 29

Had a problem similar to the second error message, except it couldn't find "fmt" or any of the standard packages when I ran dev_appserver.py

At some point I tried renaming the goroot\pkg\windows_amd64_appengine dir to goroot\pkg\windows_amd64 like it was called in the 1.8.3

and boom! it worked for some reason, though dev_appserver keeps passing the old dir name to go-app-builder

Upvotes: 2

Verran
Verran

Reputation: 4082

If you can't find a package it is usually because it is not on your local system or not where Go expects to find it. It looks like you're using windows, and I'm not completely familiar with windows as a development environment, but your file structure looks like it may be confusing the compiler.

I can say that the Go compiler will be looking for math/big in the directoryGOROOT/src/pkg/math/big where GOROOT is the location that Go runs from. So if it can't find the package, then src/pkg/math/big is not a subdirectory of the directory that Go is running from, which means you either have Go running from a bad location or the directories got messed up somehow.

Again, I'm not very familiar with windows, but from a linux terminal you can figure out where the GOROOT is using $echo $GOROOT or $which go. There may be some equivalent way of finding the directory your compiler is running from and then you can try and trace down the directory from there.

Upvotes: 0

Related Questions