[go-nuts] Why have an empty default case when sending heartbeats

2017-10-01 Thread Tamás Gulácsi 
To skip send if nothing is receiving, avoiding the block.

-- 
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.

[go-nuts] Second nested done case in a select statement

2017-10-01 Thread Tamás Gulácsi 
done may happen before value arriving from valStream.

-- 
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.

Re: [go-nuts] Rewriting a realtime game server from Node.js to Golang

2017-10-01 Thread Henrik Johansson 
No not at all. If you can write a game engine in any language you should be
fine just try to avoid too big design decisions too early so that once you
get a better grasp of Go you can more easily refactor.

mån 2 okt. 2017 kl 06:13 skrev Aaron :

> Hi I am in a process of rewriting a realtime game server from Node.js to
> Golang. It's two to three thousand lines of code in Node.js. But I have no
> previous Golang experience so it's hard to measure the workload. Do you
> think it is better for me to do some other bigger projects before I start
> rewriting my game server?
>
> --
> 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.
>

-- 
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.

[go-nuts] Why have an empty default case when sending heartbeats

2017-10-01 Thread go-question 
In the following snippet for having a function representing work send a 
heartbeat to any listeners.

Why is a select statement used in `sendPulse` instead of just executing 
`heartbeat <- struct{}{}`?
And why provide an empty default case?


doWork := func(
done <-chan interface{},
pulseInterval time.Duration,
) (<-chan interface{}, <-chan time.Time) {
heartbeat := make(chan interface{})
results := make(chan time.Time)
go func() {
defer close(heartbeat)
defer close(results)

pulse := time.Tick(pulseInterval)
workGen := time.Tick(2 * pulseInterval)

sendPulse := func() {
select { // why have a select statement?
case heartbeat <- struct{}{}:
default: // why have the default case?
}
}
sendResult := func(r time.Time) {
for {
select {
case <-done:
return
case <-pulse:
sendPulse()
case results <- r:
return
}
}
}

for {
select {
case <-done:
return
case <-pulse:
sendPulse()
case r := <-workGen:
sendResult(r)
}
}
}()
return heartbeat, results
}


-- 
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.

[go-nuts] Second nested done case in a select statement

2017-10-01 Thread go-question 
What is the purpose of the second nested <-done case in the code snippet 
below?
Wouldn't the first <-done case handle the cancellation?


orDone := func(done, c <-chan interface{}) <-chan interface{} {
valStream := make(chan interface{})
go func() {
defer close(valStream)
for {
select {
case <-done:   // first <-done case
return
case v, ok := <-c:
if ok == false {
return
}
select {
case valStream <- v:
case <-done:   // why the second nested <-done case?
}
}
}
}

-- 
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.

[go-nuts] Rewriting a realtime game server from Node.js to Golang

2017-10-01 Thread Aaron 
Hi I am in a process of rewriting a realtime game server from Node.js to 
Golang. It's two to three thousand lines of code in Node.js. But I have no 
previous Golang experience so it's hard to measure the workload. Do you 
think it is better for me to do some other bigger projects before I start 
rewriting my game server?

-- 
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.

Re: [go-nuts] Building golang libraries

2017-10-01 Thread Ian Lance Taylor 
On Fri, Sep 29, 2017 at 10:43 PM,   wrote:
>
> Can you please provide me for Ubuntu

See https://golang.org/cmd/go and https://golang.org/s/execmodes .  If
those don't help, please ask a more specific question.

Ian

-- 
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.

Re: [go-nuts] Memory issues when spawning 1 million go routines that communicate on a channel

2017-10-01 Thread Ian Lance Taylor 
On Sat, Sep 30, 2017 at 9:29 AM,   wrote:
>
> From what I understand reading and a few comments from the gopher slack,
> this is because  go is not releasing memory back to OS but holds it for a
> longer in case it needs this, if that makes sense? It would be really
> helpful, if someone could help me understand this.

Yes, that is what the Go runtime does.  It requests the memory it
needs from the operating system.  Every five minutes or so it returns
unused memory back to the operating system.  You can make this happen
sooner by calling https://golang.org/pkg/runtime/debug/#FreeOSMemory .

Note that on modern operating systems unused memory is quite cheap.

Ian

-- 
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.

Re: [go-nuts] os/exec stdout bytes.Buffer and timeout behavior?

2017-10-01 Thread Ian Lance Taylor 
On Sun, Oct 1, 2017 at 2:40 PM, roger peppe  wrote:
> One might argue that Run should respect the context deadline even in the
> presence of pipes that don't EOF.

Fair point.

Ian


> On 29 Sep 2017 22:26, "Ian Lance Taylor"  wrote:
>>
>> On Fri, Sep 29, 2017 at 12:33 PM, Alex Buchanan 
>> wrote:
>> >
>> > package main
>> >
>> > import (
>> > "bytes"
>> >   "context"
>> >   "log"
>> >   "os/exec"
>> >   "time"
>> > )
>> >
>> > func main() {
>> > var stdout bytes.Buffer
>> >
>> >   ctx, cancel := context.WithTimeout(context.Background(), time.Second)
>> >   defer cancel()
>> >
>> >   cmd := exec.CommandContext(ctx, "/bin/sh", "-c", "sleep 10; echo foo")
>> >   cmd.Stdout = 
>> >
>> >   err := cmd.Run()
>> >   log.Printf("%s, %s, '%s'", err, ctx.Err(), stdout.String())
>> > }
>> >
>> >
>> > This runs for 10 seconds, but I was expecting 1 second. Can someone help
>> > me
>> > understand what is happening? I think it has something to do with the
>> > stdout
>> > bytes.Buffer?
>>
>> Yes.  The problem is that when the context passed to CommandContext
>> expires, it kills the process started by the command, but does not
>> kill any subprocesses that that command may have started.  So when the
>> context expires the /bin/sh is killed, but the sleep subprocess is
>> still running.  Because you use a bytes.Buffer, the program has
>> created a pipe to capture the standard output of the command.  After
>> the process dies, cmd.Run is waiting for that pipe to be closed to
>> make sure that it gathers all the data.  But the pipe is held open by
>> the sleep subprocess.  It is only after that subprocess exits that the
>> pipe is closed and your program continues.
>>
>> Ian
>>
>> --
>> 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.

-- 
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.

Re: [go-nuts] os/exec stdout bytes.Buffer and timeout behavior?

2017-10-01 Thread roger peppe 
One might argue that Run should respect the context deadline even in the
presence of pipes that don't EOF.

On 29 Sep 2017 22:26, "Ian Lance Taylor"  wrote:

> On Fri, Sep 29, 2017 at 12:33 PM, Alex Buchanan 
> wrote:
> >
> > package main
> >
> > import (
> > "bytes"
> >   "context"
> >   "log"
> >   "os/exec"
> >   "time"
> > )
> >
> > func main() {
> > var stdout bytes.Buffer
> >
> >   ctx, cancel := context.WithTimeout(context.Background(), time.Second)
> >   defer cancel()
> >
> >   cmd := exec.CommandContext(ctx, "/bin/sh", "-c", "sleep 10; echo foo")
> >   cmd.Stdout = 
> >
> >   err := cmd.Run()
> >   log.Printf("%s, %s, '%s'", err, ctx.Err(), stdout.String())
> > }
> >
> >
> > This runs for 10 seconds, but I was expecting 1 second. Can someone help
> me
> > understand what is happening? I think it has something to do with the
> stdout
> > bytes.Buffer?
>
> Yes.  The problem is that when the context passed to CommandContext
> expires, it kills the process started by the command, but does not
> kill any subprocesses that that command may have started.  So when the
> context expires the /bin/sh is killed, but the sleep subprocess is
> still running.  Because you use a bytes.Buffer, the program has
> created a pipe to capture the standard output of the command.  After
> the process dies, cmd.Run is waiting for that pipe to be closed to
> make sure that it gathers all the data.  But the pipe is held open by
> the sleep subprocess.  It is only after that subprocess exits that the
> pipe is closed and your program continues.
>
> Ian
>
> --
> 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.
>

-- 
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.

[go-nuts] Re: go get exits command line in windos

2017-10-01 Thread Sotirios Mantziaris 
i think i figured it out:

git is in the latest version 2.14.2
i downgraded git to 2.14.1.windows.1 and voila all things work again.

On Sunday, October 1, 2017 at 3:39:26 PM UTC+3, Sotirios Mantziaris wrote:
>
> the log is the following:
>
> cd .
> git clone https://github.com/mantzas/adaptlog D:\dev\goprojects\src\
> github.com\mantzas\adaptlog
> cd D:\dev\goprojects\src\github.com\mantzas\adaptlog
> git submodule update --init --recursive
> cd D:\dev\goprojects\src\github.com\mantzas\adaptlog
> git show-ref
> cd D:\dev\goprojects\src\github.com\mantzas\adaptlog
> git submodule update --init --recursive
>
> the repo gets cloned BTW
>
> On Sunday, October 1, 2017 at 3:33:33 PM UTC+3, Dave Cheney wrote:
>>
>> try go get -x
>>
>> On Sunday, 1 October 2017 23:33:04 UTC+11, Sotirios Mantziaris wrote:
>>>
>>> git is available on my path
>>> windows defender (av) is disabled
>>> check out the attached gif.
>>>
>>> this was a fresh windows 10 install
>>> all component (go, git) have been installed with chocolatey.
>>> BTW: mingw works fine.
>>>
>>> can i enable some logs of go get to see what is happening?
>>>
>>> On Sunday, October 1, 2017 at 11:54:43 AM UTC+3, Dave Cheney wrote:

 Av, anti virus, software. 
>>>
>>>

-- 
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.

[go-nuts] Re: go get exits command line in windos

2017-10-01 Thread Sotirios Mantziaris 
the log is the following:

cd .
git clone https://github.com/mantzas/adaptlog 
D:\dev\goprojects\src\github.com\mantzas\adaptlog
cd D:\dev\goprojects\src\github.com\mantzas\adaptlog
git submodule update --init --recursive
cd D:\dev\goprojects\src\github.com\mantzas\adaptlog
git show-ref
cd D:\dev\goprojects\src\github.com\mantzas\adaptlog
git submodule update --init --recursive

the repo gets cloned BTW

On Sunday, October 1, 2017 at 3:33:33 PM UTC+3, Dave Cheney wrote:
>
> try go get -x
>
> On Sunday, 1 October 2017 23:33:04 UTC+11, Sotirios Mantziaris wrote:
>>
>> git is available on my path
>> windows defender (av) is disabled
>> check out the attached gif.
>>
>> this was a fresh windows 10 install
>> all component (go, git) have been installed with chocolatey.
>> BTW: mingw works fine.
>>
>> can i enable some logs of go get to see what is happening?
>>
>> On Sunday, October 1, 2017 at 11:54:43 AM UTC+3, Dave Cheney wrote:
>>>
>>> Av, anti virus, software. 
>>
>>

-- 
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.

[go-nuts] Re: go get exits command line in windos

2017-10-01 Thread Sotirios Mantziaris 





On Sunday, October 1, 2017 at 3:33:04 PM UTC+3, Sotirios Mantziaris wrote:
>
> git is available on my path
> windows defender (av) is disabled
> check out the attached gif.
>
> this was a fresh windows 10 install
> all component (go, git) have been installed with chocolatey.
> BTW: mingw works fine.
>
> can i enable some logs of go get to see what is happening?
>
> On Sunday, October 1, 2017 at 11:54:43 AM UTC+3, Dave Cheney wrote:
>>
>> Av, anti virus, software. 
>
>

-- 
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.

[go-nuts] Re: go get exits command line in windos

2017-10-01 Thread Sotirios Mantziaris 
git is available on my path
windows defender (av) is disabled
check out the attached gif.

this was a fresh windows 10 install
all component (go, git) have been installed with chocolatey.
BTW: mingw works fine.

can i enable some logs of go get to see what is happening?

On Sunday, October 1, 2017 at 11:54:43 AM UTC+3, Dave Cheney wrote:
>
> Av, anti virus, software. 

-- 
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.

[go-nuts] Re: go get exits command line in windos

2017-10-01 Thread Dave Cheney 
try go get -x

On Sunday, 1 October 2017 23:33:04 UTC+11, Sotirios Mantziaris wrote:
>
> git is available on my path
> windows defender (av) is disabled
> check out the attached gif.
>
> this was a fresh windows 10 install
> all component (go, git) have been installed with chocolatey.
> BTW: mingw works fine.
>
> can i enable some logs of go get to see what is happening?
>
> On Sunday, October 1, 2017 at 11:54:43 AM UTC+3, Dave Cheney wrote:
>>
>> Av, anti virus, software. 
>
>

-- 
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.

[go-nuts] Re: git submodule vs normal go vendoring

2017-10-01 Thread paul . totterman 

>
> can anyone tell me the pros/cons of using git submodule update instead of 
> godep govendor etc... ?


We used to use git submodules, but have now switched to 
https://github.com/golang/dep . Much recommended.

Cheers,
Paul 

-- 
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.

[go-nuts] Re: Link not performed when 'go install'

2017-10-01 Thread Hallgeir Holien 

Thank you!

On Sunday, October 1, 2017 at 12:50:51 PM UTC+2, Dave Cheney wrote:
>
> The command you want is
>
> go get -u github.com/golang/dep/cmd/dep
>
> You should never need the -a flag unless something is broken with your Go 
> installation, so you should fix that, not apply -a unconditionally. 
>
>

-- 
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.

[go-nuts] Re: Link not performed when 'go install'

2017-10-01 Thread Dave Cheney 
The command you want is

go get -u github.com/golang/dep/cmd/dep

You should never need the -a flag unless something is broken with your Go 
installation, so you should fix that, not apply -a unconditionally. 

-- 
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.

[go-nuts] Re: Link not performed when 'go install'

2017-10-01 Thread Hallgeir Holien 
The full command is

go get -a -x github.com/golang/dep &> goact.txt

The output is attached.


On Sunday, October 1, 2017 at 10:39:52 AM UTC+2, Dave Cheney wrote:
>
> Linking will only be performed if the package you go get'd is a main 
> package.
>
> For example
>
> go get golang.org/x/tools
>
> Will get the tools repo, but will not build any commands because the 
> commands are in the path
>
> go get golang.org/x/tools/cmd/...
>
> What is the full command you ran, and what is the full output you received?
>
> Thanks
>
> Dave
>
>
> On Sunday, 1 October 2017 04:16:58 UTC, Hallgeir Holien wrote:
>>
>> My Go environment(on Ubuntu 16.04 and several versions of go, including 
>> 1.9) no longer builds the executable. 
>> I have previously been able to run go get and go install to build 
>> executables to the bin folder using go1.8.3.
>> Now, for some reason I do not get any executables.
>> After this happened I installed gvm to try using other go versions. All 
>> behave similar.
>> I have used 'git get -x -a' to inspect the actions performed and see that 
>> all compile steps are run ok, so I get the .a files ok.
>> However I can not see that any link actions are called. The last action 
>> listed is a mv on an .a file.
>> Any ideas on how to fix this?
>>
>>

-- 
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.
WORK=/tmp/go-build459737979
mkdir -p $WORK/runtime/internal/sys/_obj/
mkdir -p $WORK/runtime/internal/
cd /home/hallgeir/.gvm/gos/go1.9/src/runtime/internal/sys
/home/hallgeir/.gvm/gos/go1.9/pkg/tool/linux_amd64/compile -o 
$WORK/runtime/internal/sys.a -trimpath $WORK -goversion go1.9 -p 
runtime/internal/sys -std -+ -complete -buildid 
a542d7437edd7d5c680c251aedd309d42e1baa12 -D 
_/home/hallgeir/.gvm/gos/go1.9/src/runtime/internal/sys -I $WORK -pack 
./arch.go ./arch_amd64.go ./intrinsics.go ./stubs.go ./sys.go 
./zgoarch_amd64.go ./zgoos_linux.go ./zversion.go
mkdir -p /home/hallgeir/.gvm/gos/go1.9/pkg/linux_amd64/runtime/internal/
mv $WORK/runtime/internal/sys.a 
/home/hallgeir/.gvm/gos/go1.9/pkg/linux_amd64/runtime/internal/sys.a
mkdir -p $WORK/runtime/internal/atomic/_obj/
cd /home/hallgeir/.gvm/gos/go1.9/src/runtime/internal/atomic
/home/hallgeir/.gvm/gos/go1.9/pkg/tool/linux_amd64/compile -o 
$WORK/runtime/internal/atomic.a -trimpath $WORK -goversion go1.9 -p 
runtime/internal/atomic -std -+ -buildid 
bea2bdc76dc69f40a74a2f12862b2cf71c4f7553 -D 
_/home/hallgeir/.gvm/gos/go1.9/src/runtime/internal/atomic -I $WORK -pack 
-asmhdr $WORK/runtime/internal/atomic/_obj/go_asm.h ./atomic_amd64x.go 
./stubs.go
/home/hallgeir/.gvm/gos/go1.9/pkg/tool/linux_amd64/asm -trimpath $WORK -I 
$WORK/runtime/internal/atomic/_obj/ -I 
/home/hallgeir/.gvm/gos/go1.9/pkg/include -D GOOS_linux -D GOARCH_amd64 -o 
$WORK/runtime/internal/atomic/_obj/asm_amd64.o ./asm_amd64.s
pack r $WORK/runtime/internal/atomic.a 
$WORK/runtime/internal/atomic/_obj/asm_amd64.o # internal
mv $WORK/runtime/internal/atomic.a 
/home/hallgeir/.gvm/gos/go1.9/pkg/linux_amd64/runtime/internal/atomic.a
mkdir -p $WORK/runtime/_obj/
mkdir -p $WORK/
cd /home/hallgeir/.gvm/gos/go1.9/src/runtime
/home/hallgeir/.gvm/gos/go1.9/pkg/tool/linux_amd64/compile -o $WORK/runtime.a 
-trimpath $WORK -goversion go1.9 -p runtime -std -+ -buildid 
bac9172adcea874907aaf3f5cd6ebd40efe94d12 -D 
_/home/hallgeir/.gvm/gos/go1.9/src/runtime -I $WORK -pack -asmhdr 
$WORK/runtime/_obj/go_asm.h ./alg.go ./atomic_pointer.go ./cgo.go ./cgo_mmap.go 
./cgo_sigaction.go ./cgocall.go ./cgocallback.go ./cgocheck.go ./chan.go 
./compiler.go ./complex.go ./cpuflags_amd64.go ./cpuprof.go ./cputicks.go 
./debug.go ./defs_linux_amd64.go ./env_posix.go ./error.go ./extern.go 
./fastlog2.go ./fastlog2table.go ./float.go ./hash64.go ./hashmap.go 
./hashmap_fast.go ./heapdump.go ./iface.go ./lfstack.go ./lfstack_64bit.go 
./lock_futex.go ./malloc.go ./mbarrier.go ./mbitmap.go ./mcache.go 
./mcentral.go ./mem_linux.go ./mfinal.go ./mfixalloc.go ./mgc.go ./mgclarge.go 
./mgcmark.go ./mgcsweep.go ./mgcsweepbuf.go ./mgcwork.go ./mheap.go ./mprof.go 
./msan0.go ./msize.go ./mstats.go ./netpoll.go ./netpoll_epoll.go ./os_linux.go 
./os_linux_generic.go ./panic.go ./plugin.go ./print.go ./proc.go ./profbuf.go 
./proflabel.go ./race0.go ./rdebug.go ./relax_stub.go ./runtime.go 
./runtime1.go ./runtime2.go ./rwmutex.go ./select.go ./sema.go 
./signal_amd64x.go ./signal_linux_amd64.go ./signal_sighandler.go 
./signal_unix.go ./sigqueue.go ./sigtab_linux_generic.go ./sizeclasses.go 
./slice.go ./softfloat64.go ./sqrt.go ./stack.go ./string.go ./stubs.go 
./stubs2.go ./stubs_asm.go ./stubs_linux.go ./symtab.go ./sys_nonppc64x.go 
./sys_x86.go ./time.go ./timestub.go ./trace.go ./traceback.go ./type.go 
./typekind.go ./unaligned1.go ./utf8.go ./vdso_linux_amd64.go

[go-nuts] go get exits command line in windos

2017-10-01 Thread Dave Cheney 
Av, anti virus, software. 

-- 
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.

[go-nuts] go get exits command line in windos

2017-10-01 Thread Dave Cheney 
Go get shells out to git, is git available in your path? Also, most problems 
with windows are caused by an software, can you try disabling it ?

-- 
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.

[go-nuts] go get exits command line in windos

2017-10-01 Thread Sotirios Mantziaris 
Hi,

after a re-installation of windows 10 where go get was working fine it does 
not work now.
Every go command works fine except for go get which terminates the command 
line.
Any ideas?

-- 
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.

[go-nuts] Re: Link not performed when 'go install'

2017-10-01 Thread Dave Cheney 
Linking will only be performed if the package you go get'd is a main 
package.

For example

go get golang.org/x/tools

Will get the tools repo, but will not build any commands because the 
commands are in the path

go get golang.org/x/tools/cmd/...

What is the full command you ran, and what is the full output you received?

Thanks

Dave


On Sunday, 1 October 2017 04:16:58 UTC, Hallgeir Holien wrote:
>
> My Go environment(on Ubuntu 16.04 and several versions of go, including 
> 1.9) no longer builds the executable. 
> I have previously been able to run go get and go install to build 
> executables to the bin folder using go1.8.3.
> Now, for some reason I do not get any executables.
> After this happened I installed gvm to try using other go versions. All 
> behave similar.
> I have used 'git get -x -a' to inspect the actions performed and see that 
> all compile steps are run ok, so I get the .a files ok.
> However I can not see that any link actions are called. The last action 
> listed is a mv on an .a file.
> Any ideas on how to fix this?
>
>

-- 
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.

Re: [go-nuts] git submodule vs normal go vendoring

2017-10-01 Thread Peter Mogensen 


On 2017-10-01 06:38, JM wrote:
> can anyone tell me the pros/cons of using git submodule update instead
> of godep govendor etc... ?
> 
> git submodule update --init --recursive

Your build depend on that command succeeding.
If sub-repos are not under your control that can be a serious problem
for reproducible build - or builds at all.

/Peter

-- 
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.