Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gonum BLAS (cgo) broken in Go 1.6 #129

Open
njern opened this issue Feb 24, 2016 · 1 comment
Open

Gonum BLAS (cgo) broken in Go 1.6 #129

njern opened this issue Feb 24, 2016 · 1 comment

Comments

@njern
Copy link
Collaborator

njern commented Feb 24, 2016

I just did a "fresh install" of GoLearn for a project I am working on and noticed that it breaks under Go 1.6 with the following errors:

  • .../src/github.com/sjwhitworth/golearn/ensemble/multisvc_test.go
    Line 17: - runtime error: cgo argument has Go pointer to Go pointer
  • .../src/github.com/sjwhitworth/golearn/ensemble/multisvc_test.go
    Line 40: - runtime error: cgo argument has Go pointer to Go pointer
  • .../src/github.com/sjwhitworth/golearn/linear_models/linear_models_test.go
    Line 21: - runtime error: cgo argument has Go pointer to Go pointer
  • .../src/github.com/sjwhitworth/golearn/meta/one_v_all_test.go
    Line 29: - runtime error: cgo argument has Go pointer to Go pointer

You can reproduce by running the tests for the project on a machine with Go 1.6 installed.

This has to do with these new restrictions for cgo , introduced in Go 1.6. Other projects have noticed this breaking cgo stuff as well.

Does anyone feel like digging into this? It seems BLAS dependency has spread across the code base since I touched it last.... 😢

@yukota
Copy link

yukota commented May 2, 2016

I reproduced same problem in using LinearSVC.
I temporize with
export GODEBUG=cgocheck=0

Sentimentron added a commit to Sentimentron/golearn that referenced this issue May 21, 2016
Fixes sjwhitworth#133 and sjwhitworth#134, temporary workaround for sjwhitworth#129 so we can continue
testing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants