[go-nuts] How do you get an update for the tip of a package?

2021-03-03 Thread Peter Kleiweg
I try to install a Go program from github at tip. This works: go get github.com/some/program@HEAD But when there is a new push to the repository, and I do this: go get -u github.com/some/program@HEAD ... I still have the previous version. The same with go install. The same when I

Re: [go-nuts] How do you test an unpublished module?

2021-02-20 Thread Peter Kleiweg
cts the changes made in the package. This is exactly what I need. Op zaterdag 20 februari 2021 om 13:45:15 UTC+1 schreef ohir: > Dnia 2021-02-20, o godz. 04:10:38 > Peter Kleiweg napisał(a): > > > Suppose I am writing a package that is in its own module, and I want > > to test

[go-nuts] How do you test an unpublished module?

2021-02-20 Thread Peter Kleiweg
Suppose I am writing a package that is in its own module, and I want to test it. Not with unit tests, but with a larger program that uses other non-standard packages as well. Before modules, I would develop the package in ~/go/src, write the test program somewhere else, and import the package.

[go-nuts] Re: go get not working in Go 1.16

2021-02-16 Thread Peter Kleiweg
Op dinsdag 16 februari 2021 om 21:40:52 UTC+1 schreef Ian Lance Taylor: > On Tue, Feb 16, 2021 at 12:34 PM Peter Kleiweg wrote: > > > > `go get` is broken. It doesn't download packages. > > Tell us what you did, what you expected to happen, and what happened > in

[go-nuts] Re: Go 1.16 is released

2021-02-16 Thread Peter Kleiweg
`go get` is broken. It doesn't download packages. Op dinsdag 16 februari 2021 om 20:56:37 UTC+1 schreef Alex Rakoczy: > Hello gophers, > > We just released Go 1.16 > > To find out what has changed in Go 1.16, read the release notes: > https://golang.org/doc/go1.16 > > You can download binary and

Re: [go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-28 Thread Peter Kleiweg
Op vrijdag 28 februari 2020 16:57:00 UTC+1 schreef Ian Lance Taylor: > > On Fri, Feb 28, 2020 at 7:18 AM Peter Kleiweg > wrote: > > > > Op vrijdag 28 februari 2020 16:13:50 UTC+1 schreef Robert Engels: > >> > >> > >> Can you clarify that

Re: [go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-28 Thread Peter Kleiweg
--- > From: Peter Kleiweg > Sent: Feb 28, 2020 9:04 AM > To: golang-nuts > Subject: [go-nuts] Re: Lot's of test errors in package zmq4 with Go > version 1.14, no errors with earlier versions > > Retry after EINTR solved the code lock-up too. > > Op woensdag 26 febru

[go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-28 Thread Peter Kleiweg
Retry after EINTR solved the code lock-up too. Op woensdag 26 februari 2020 12:33:05 UTC+1 schreef Peter Kleiweg: > > With Go version 1.14 I get a lot of errors when I run: > > go test -v github.com/pebbe/zmq4 > > I didn't see this with Go 1.13.8 or any earlier version. >

Re: [go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-27 Thread Peter Kleiweg
get the interrupted system calls, so I have to fix those too. It looks like these are two different issues. Op donderdag 27 februari 2020 19:07:54 UTC+1 schreef Robert Engels: > > Does it freeze if you use GODEBUG=noasyncpreempt=1 ? > > -Original Message----- > From: Peter

Re: [go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-27 Thread Peter Kleiweg
Op donderdag 27 februari 2020 18:50:56 UTC+1 schreef Ian Lance Taylor: > > On Thu, Feb 27, 2020 at 9:41 AM Robert Engels > wrote: > > > > > > I re-read your comments, and I agree that a rare error is still and > error, and needs to be handled, but if it the platform is introducing lots > of

Re: [go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-26 Thread Peter Kleiweg
ay, February 26, 2020 at 3:51:54 PM UTC+1, Peter Kleiweg > wrote: > >> > >> Op woensdag 26 februari 2020 13:05:40 UTC+1 schreef Manlio Perillo: > >>> > >>> On Wednesday, February 26, 2020 at 12:33:05 PM UTC+1, Peter Kleiweg > wrote:

[go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-26 Thread Peter Kleiweg
Op woensdag 26 februari 2020 13:05:40 UTC+1 schreef Manlio Perillo: > > On Wednesday, February 26, 2020 at 12:33:05 PM UTC+1, Peter Kleiweg wrote: >> >> With Go version 1.14 I get a lot of errors when I run: >> >> go test -v github.com/pebbe/zmq4 >> >&g

[go-nuts] Re: Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-26 Thread Peter Kleiweg
This is with go version go1.14 linux/amd64 Op woensdag 26 februari 2020 12:33:05 UTC+1 schreef Peter Kleiweg: > > With Go version 1.14 I get a lot of errors when I run: > > go test -v github.com/pebbe/zmq4 > > I didn't see this with Go 1.13.8 or any earlier version. >

[go-nuts] Lot's of test errors in package zmq4 with Go version 1.14, no errors with earlier versions

2020-02-26 Thread Peter Kleiweg
With Go version 1.14 I get a lot of errors when I run: go test -v github.com/pebbe/zmq4 I didn't see this with Go 1.13.8 or any earlier version. Is this a problem with Go 1.14, or am I doing something wrong and just got lucky until now? How do I debug this? The errors are different for

[go-nuts] Re: [security] Go 1.13.2 and Go 1.12.11 are released

2019-10-17 Thread Peter Kleiweg
I did a git pull. There is a tag go1.13.1, but no tag go1.13.2. Also, no tag go1.12.11. -- 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

[go-nuts] identifier ... may conflict with identifiers generated by cgo

2019-01-21 Thread Peter Kleiweg
Installing packages with go1.12beta2 I get these messages: ... github.com/rug-compling/alpinocorpus-go/alpinocorpus/reader.go:39:15: identifier "_Ctype_alpinocorpus_iter" may conflict with identifiers generated by cgo ...

Re: [go-nuts] Go 1.12 Beta 1 is released

2018-12-20 Thread Peter Kleiweg
Ian Lance Taylor schreef op 20 december 2018 23:10:17 CET: > On Thu, Dec 20, 2018 at 10:58 AM Peter Kleiweg > wrote: > > > > Ian Lance Taylor schreef op 20 december 2018 > 19:20:13 CET: > > > Adding the file with the local configuration should work just as > w

Re: [go-nuts] Go 1.12 Beta 1 is released

2018-12-20 Thread Peter Kleiweg
Ian Lance Taylor schreef op 20 december 2018 19:20:13 CET: > On Thu, Dec 20, 2018 at 8:02 AM Peter Kleiweg > wrote: > > > > Ian Lance Taylor schreef op 20 december 2018 > 16:47:20 CET: > > > On Thu, Dec 20, 2018 at 1:07 AM Peter Kleiweg > > > wrote: >

Re: [go-nuts] Go 1.12 Beta 1 is released

2018-12-20 Thread Peter Kleiweg
Ian Lance Taylor schreef op 20 december 2018 16:47:20 CET: > On Thu, Dec 20, 2018 at 1:07 AM Peter Kleiweg > wrote: > > > > Ian Lance Taylor schreef op 20 december 2018 > 00:06:58 CET: > > > > > How about this: > > > > > > Move the

Re: [go-nuts] Go 1.12 Beta 1 is released

2018-12-20 Thread Peter Kleiweg
configuration, a file that imports '"C" and sets CFLAGS and LDFLAGS, without modifying the official package files. This works, except for packages that rely on pkg-config. I don't see how I can modify the contents of PKG_CONFIG_PATH in a Go file. -- Peter Kleiweg http://pkleiweg.h

Re: [go-nuts] Go 1.12 Beta 1 is released

2018-12-19 Thread Peter Kleiweg
Ian Lance Taylor schreef op 19 december 2018 23:27:13 CET: > On Wed, Dec 19, 2018 at 2:15 PM Peter Kleiweg > wrote: > > > > > I assume that the recompile fails because compiling the C code > fails. > > You should compile the C code yourself, producing a .syso file.

Re: [go-nuts] Go 1.12 Beta 1 is released

2018-12-19 Thread Peter Kleiweg
> I assume that the recompile fails because compiling the C code fails. You should compile the C code yourself, producing a .syso file. You should add that .syso file to your package directory. You should remove the C code from your package directory--you can still put it in a subdirectory, of

Re: [go-nuts] Go 1.12 Beta 1 is released

2018-12-19 Thread Peter Kleiweg
How do I do what runtime/race does? Is it what I want? I have a package with C and Go files. I want to install that package. Then I want to import that package into a program, and build that program without recompiling the package. Because recompile fails. How do I do that? This was an issue

[go-nuts] Go 1.12 Beta 1 is released

2018-12-18 Thread Peter Kleiweg
Go 1.12 is the last release that will support binary-only packages. What are the alternatives? I need binary-only packages for packages that use cgo with non-standard environment variable values. -- You received this message because you are subscribed to the Google Groups "golang-nuts"

Re: [go-nuts] Problems with cache

2018-08-25 Thread Peter Kleiweg
Op zaterdag 25 augustus 2018 19:06:27 UTC+2 schreef Sebastien Binet: > > > > On Sat, Aug 25, 2018 at 6:54 PM Ian Lance Taylor > wrote: > >> On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg > > wrote: >> > Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef

Re: [go-nuts] Problems with cache

2018-08-25 Thread Peter Kleiweg
Op zaterdag 25 augustus 2018 18:54:32 UTC+2 schreef Ian Lance Taylor: > > On Sat, Aug 25, 2018 at 7:58 AM, Peter Kleiweg > wrote: > > Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg: > >> > >> On 25 Aug 2018, at 15:21, Peter Kleiweg wrote: >

Re: [go-nuts] Problems with cache

2018-08-25 Thread Peter Kleiweg
Op zaterdag 25 augustus 2018 16:40:55 UTC+2 schreef Jakob Borg: > > On 25 Aug 2018, at 15:21, Peter Kleiweg > > wrote: > > > disabling the cache won't be an option in Go 1.12. What to do then? > > > You don’t say what your issues with the build cache are. If you did

[go-nuts] Problems with cache

2018-08-25 Thread Peter Kleiweg
Since Go 1.10, the cache causes many headaches. You can disable the cache with GOCACHE=off. Unless you work on mega projects, you don't need a cache anyway. But disabling the cache won't be an option in Go 1.12. What to do then? Stick with old version of Go? The release notes for Go 1.11 have

[go-nuts] Uncontrolled map access can crash the program --- how?

2017-07-05 Thread Peter Kleiweg
>From the faq: https://golang.org/doc/faq#atomic_maps ... uncontrolled map access can crash the program. In what situations does this apply? Can I have two goroutines reading a single map at the same time? Can I have one goroutine putting something in a map while at the same time another

[go-nuts] To panic or not to panic, that's the question

2017-05-31 Thread Peter Kleiweg
If a package can't be used because some precondition can't be fulfilled, you can use a panic. Then the whole program will crash at start-up. The alternative would be to not panic in the init, but have all function calls return an error. If the package is used in a large program, part of it may

Re: [go-nuts] Are these types discarded? Is this a compiler bug?

2017-03-24 Thread Peter Kleiweg
Op donderdag 23 maart 2017 20:58:53 UTC+1 schreef Ian Lance Taylor: > > On Thu, Mar 23, 2017 at 11:56 AM, Peter Kleiweg <pkle...@xs4all.nl > > wrote: > > Op donderdag 23 maart 2017 17:46:18 UTC+1 schreef Ian Lance Taylor: > >> > >> On Thu, Mar 2

Re: [go-nuts] Are these types discarded? Is this a compiler bug?

2017-03-23 Thread Peter Kleiweg
Op donderdag 23 maart 2017 17:46:18 UTC+1 schreef Ian Lance Taylor: > > On Thu, Mar 23, 2017 at 8:54 AM, Peter Kleiweg <pkle...@xs4all.nl > > wrote: > > Some code that includes C code compiles fine on Linux, but gives strange > > errors on Darwin. > > > >

[go-nuts] Are these types discarded? Is this a compiler bug?

2017-03-23 Thread Peter Kleiweg
Some code that includes C code compiles fine on Linux, but gives strange errors on Darwin. In one source file, that doesn't include C, I have this: type reactor_socket struct { e State

[go-nuts] Go 1.8 : cmd/go : test timed out after 3m0s

2017-02-17 Thread Peter Kleiweg
Installing Go 1.8 with: git pull git checkout go1.8 cd src GOROOT_BOOTSTRAP=/path/to/go1.4 ./all.bash I get this: panic: test timed out after 3m0s (stacktrace) FAILcmd/go 193.895s The problem is I am installing this on a system with a very slow, network file

Re: [go-nuts] xml omitempty for sub-elements

2016-12-08 Thread Peter Kleiweg
Four years later, and this still hasn't been fixed. The conversation you are linking to has been locked. What can we do? File a new bug report? Op donderdag 15 november 2012 13:41:55 UTC+1 schreef Vladimir Mihailenco: > > I guess you have to vote for >

Re: [go-nuts] Go 1.7.3 is released

2016-10-19 Thread Peter Kleiweg
Same problem here. Also, after the last package test cmd/vet/internal/cfg, all further tests are skipped. GOARCH="amd64" GOBIN="" GOEXE="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="/net/aps/64/opt/gosite" GORACE="" GOROOT="/net/aps/64/opt/go"

[go-nuts] Re: Request for advice: Developing for Android

2016-09-23 Thread Peter Kleiweg
Op donderdag 22 september 2016 19:53:17 UTC+2 schreef Elias Naur: Does subsequent go gets after rm -fr'ing once, or only if you rm -fr before > go get every time? If it works from now on, you might have had some old > crud in the existing directory. If you need rm -fr every time, here's the >

[go-nuts] Re: Request for advice: Developing for Android

2016-09-23 Thread Peter Kleiweg
Op vrijdag 23 september 2016 04:12:47 UTC+2 schreef parais...@gmail.com: > > My advice, unless you need to do some low level stuff with the NDK in C or > C++ use Java, that's the only viable way to develop for Android. > > With Phonegap (html,javascript) you will never take advantage of Android

[go-nuts] Re: Request for advice: Developing for Android

2016-09-22 Thread Peter Kleiweg
Op donderdag 22 september 2016 18:28:43 UTC+2 schreef Peter Kleiweg: > > Op donderdag 22 september 2016 18:08:10 UTC+2 schreef Elias Naur: >> >> >> >> On Thursday, September 22, 2016 at 5:34:24 PM UTC+2, Peter Kleiweg wrote: >>> >>> I try the examp

[go-nuts] Re: Request for advice: Developing for Android

2016-09-22 Thread Peter Kleiweg
Op donderdag 22 september 2016 18:08:10 UTC+2 schreef Elias Naur: > > > > On Thursday, September 22, 2016 at 5:34:24 PM UTC+2, Peter Kleiweg wrote: >> >> I try the examples on https://github.com/golang/go/wiki/Mobile >> >> Native applications -> Build

[go-nuts] Re: Request for advice: Developing for Android

2016-09-22 Thread Peter Kleiweg
I try the examples on https://github.com/golang/go/wiki/Mobile Native applications -> Building and deploying to Android works fine. On "SDK applications and generating bindings" I get into problems. It says: go get -d golang.org/x/mobile/example/bind/... I get: warning:

[go-nuts] Request for advice: Developing for Android

2016-09-21 Thread Peter Kleiweg
I want to start developing for Android, and would like your advice on that: Where to start. My background is Linux. I have a lot of programming experience. Mainly C and Perl, followed by C and Python, and for the last five years it's mainly Go. I did some Java programming for a few weeks,

[go-nuts] Append to slice... what happens?

2016-06-26 Thread Peter Kleiweg
This: https://play.golang.org/p/AE670rTMpE I don't know what I expected, but it's weird. Don't mess with slices. -- 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

[go-nuts] Re: Discussion on "Vendoring edge case, critical problem"

2016-06-19 Thread Peter Kleiweg
Libraries can vendor in the directory "internal"? -- 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,