I have recently been reflecting about OrangeFS and AMD's HSA and how they
eventually reach golang users. That implies somewhere there will be a
cgogen generated wrapper for them somehow, then they will be used.
What if OrangeFS' and HSA were deeply embedded into the go language
themselves in
for the moment.
On Wednesday, August 10, 2016 at 10:00:37 AM UTC-4, David Marceau wrote:
>
> when I install from sources straight from git checkout go1.7rc6
> go1.7rc6 FAILS on Asus Z97-A-USB31 motherboard with intel i5-4590,
> "../misc/cgo/testsanitizers"
> it core
ed the residue CXX pointing to g++ so it should be built using this
instead:
CC=/usr/bin/clang CXX=/usr/bin/clang++
GOROOT_BOOTSTRAP=/root/SQstuff/go1.7rc5 ./make.bash
On Thursday, August 11, 2016 at 11:30:54 AM UTC-4, David Marceau wrote:
>
>
> On ArchLinux with a previously gcc built
because it was confused as to what CC it should
be using since I had both gcc and clang installed on my box.
On Wednesday, August 10, 2016 at 1:07:50 PM UTC-4, Ian Lance Taylor wrote:
>
> On Wed, Aug 10, 2016 at 7:00 AM, David Marceau
> <uticdmar...@gmail.com > wrote:
&g
when I install from sources straight from git checkout go1.7rc6
go1.7rc6 FAILS on Asus Z97-A-USB31 motherboard with intel i5-4590,
"../misc/cgo/testsanitizers"
it core dumps and doesn't give me the success message to start using it as
the previous go1.7rc[1-4] did.
signal: segmentation fault
com/limit-https-listener/
>
> tcpKeepAliveListener ended up being the only code that was copied but not
> specialized. It would have been nice if it were exported from the http
> package.
>
> On Thursday, August 4, 2016 at 12:27:18 AM UTC+2, David Marceau wrote:
>&
I tried just what you mentioned. Unfortunately even my interim solution
when it is outside of the net.http package and within mine, there are many
services that are not exported meaning I can't use them at all and the
variables themselves are inaccessible.
I tried copying pasting some
I perused your blog entry you mentioned. It's very interesting and will
come in handy in the future. Thank you.
I can appreciate your point of view about accepting the fact that currently
listeners are not part of the Server and just proceed to produce code and
get it done ASAP. My
Another question: Why wasn't tlsListener placed as part of the Server structure?
I think it makes sense to place it there since it is the server that creates
and uses it.
It also makes sense to expose it to tweak it as some might more control over it
and in this case the constraining the
nCount)?
I'm doing my best not to tweak/recompile golang's sources to introduce this
limitlistener feature to a tls server.
I was hoping someone had a trick to avoid that.
Thank you.
David Marceau
--
You received this message because you are subscribed to the Google Groups
"golang-nuts&qu
efore the serveFile.
That's all. Thanks to everyone who dropped by.
On Friday, June 24, 2016 at 9:44:00 AM UTC-4, David Marceau wrote:
>
> Here is what is in my import. Maybe I should be looking in goji instead
> of net/http?
>
>
> import (
> "fmt&q
11 matches
Mail list logo