I'm sorry that I can't help more. It appears to me that the go builder was able to create some of the temporary files it needs, but not others. This is a very strange situation that I have not seen before. Akin to having a full disk or otherwise exhausting the storage availability.
I do not know how to diagnose any more of this on windows. Apologies. On Tue, Apr 30, 2019 at 1:11 PM Avetis Sargsian <avetissargs...@gmail.com> wrote: > > Ok there is one file in > E:\temp\go-build828919622\b001\importcfg.link > end is empty in > E:\temp\go-build828919622\b001\exe > > this is content of importcfg.link > packagefile > hello=C:\Users\Avetis\AppData\Local\go-build\ae\aecfeab49f117df031d74e0ca3aad783ba25f0524b981cbb74a2db671205fadd-d > packagefile fmt=C:\Go\pkg\windows_amd64\fmt.a > packagefile runtime=C:\Go\pkg\windows_amd64\runtime.a > packagefile errors=C:\Go\pkg\windows_amd64\errors.a > packagefile internal/fmtsort=C:\Go\pkg\windows_amd64\internal\fmtsort.a > packagefile io=C:\Go\pkg\windows_amd64\io.a > packagefile math=C:\Go\pkg\windows_amd64\math.a > packagefile os=C:\Go\pkg\windows_amd64\os.a > packagefile reflect=C:\Go\pkg\windows_amd64\reflect.a > packagefile strconv=C:\Go\pkg\windows_amd64\strconv.a > packagefile sync=C:\Go\pkg\windows_amd64\sync.a > packagefile unicode/utf8=C:\Go\pkg\windows_amd64\unicode\utf8.a > packagefile internal/bytealg=C:\Go\pkg\windows_amd64\internal\bytealg.a > packagefile internal/cpu=C:\Go\pkg\windows_amd64\internal\cpu.a > packagefile > runtime/internal/atomic=C:\Go\pkg\windows_amd64\runtime\internal\atomic.a > packagefile > runtime/internal/math=C:\Go\pkg\windows_amd64\runtime\internal\math.a > packagefile > runtime/internal/sys=C:\Go\pkg\windows_amd64\runtime\internal\sys.a > packagefile sort=C:\Go\pkg\windows_amd64\sort.a > packagefile sync/atomic=C:\Go\pkg\windows_amd64\sync\atomic.a > packagefile math/bits=C:\Go\pkg\windows_amd64\math\bits.a > packagefile internal/poll=C:\Go\pkg\windows_amd64\internal\poll.a > packagefile > internal/syscall/windows=C:\Go\pkg\windows_amd64\internal\syscall\windows.a > packagefile internal/testlog=C:\Go\pkg\windows_amd64\internal\testlog.a > packagefile syscall=C:\Go\pkg\windows_amd64\syscall.a > packagefile time=C:\Go\pkg\windows_amd64\time.a > packagefile unicode/utf16=C:\Go\pkg\windows_amd64\unicode\utf16.a > packagefile unicode=C:\Go\pkg\windows_amd64\unicode.a > packagefile internal/race=C:\Go\pkg\windows_amd64\internal\race.a > packagefile > internal/syscall/windows/sysdll=C:\Go\pkg\windows_amd64\internal\syscall\windows\sysdll.a > packagefile > internal/syscall/windows/registry=C:\Go\pkg\windows_amd64\internal\syscall\windows\registry.a > > вт, 30 апр. 2019 г. в 18:57, andrey mirtchovski <mirtchov...@gmail.com>: >> >> > PS F:\GoWorckspace\src\hello> go build -work >> > WORK=E:\temp\go-build828919622 >> > open E:\temp\go-build828919622\b001\exe\a.out.exe: The system cannot find >> > the file specified. >> >> once you have done this you should be able to cd to >> E:\temp\go-build828919622 and look around to see if any files have >> been created, including b001\exe\a.out.exe. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
