Win32 (experimental) build of release 2011-02-15

Skip to first unread message

Joe Poirier

Feb 15, 2011, 6:29:02 PM2/15/11
to golang-nuts

An alternative distribution medium for obtaining the Go toolchain is
Npackd, a windows package manager:

Note the 32-bit (i386) version of the GO compiler and linker are
8g.exe and 8l.exe respectively.


The zip file and installer both contain the pre-built Go toolchain and
a snapshot of the release source tree, /excluding/ the mercurial
repository metadata. Although the source code is included in the
distribution it's untracked from mercurial's point of view, therefore
hg commands like "hg pull" and "hg update" from within the Go folder
won't work.

If you'd like to build the Go toolchain on your own, and I encourage
you to do so, you'll need a build environment and the dependencies
(e.g. make, hg, gcc, etc.) to do so. Here's a complete, /no/
installation required, package that also comes with some really cool
*nix command-line tools and a nifty *nix shell to play with-thanks to
the fine MinGW/MSYS folks-have a peek at the readme to get going:
Go build information can be found on the golang website:

Check out Mateusz Czaplinski's gowin-env package, "a Minimal companion
environment to make canonical Makefiles of the Google Go project work
in vanilla Windows," that you can use in conjunction with the Go
tool. /No/ installation required:

If you don't already have a favorite Go source code editor for windows
check out GolangIDE:

And ff you're just starting out with Go on windows I have a short
screen-cast entitled "Beginner's Guide Using Go On Win98/2K/XP" that
you may find helpful:


Feb 15, 2011, 10:34:22 PM2/15/11
to golang-nuts
Thanks for this language!

Jul 28, 2018, 2:43:04 PM7/28/18
to golang-nuts
i need the package w32 for x86 a zip file

Jan Mercl

Jul 28, 2018, 3:00:26 PM7/28/18
to, golang-nuts
On Sat, Jul 28, 2018 at 8:42 PM <> wrote:

> i need the package w32 for x86 a zip file

Get the Go project repository, checkout the proper commit and try to build if from sources. There's a chance it will not build anymore using the current environment of your machine being possibly 7 years in the future.

Do you need that exact version? Can you adjust your task to use the current release (Go1.10.3)? It might be easier than attempting to revive such an old, unsupported release.



Reply all
Reply to author
0 new messages