lgo icon indicating copy to clipboard operation
lgo copied to clipboard

Installation failure on go1.12

Open ryanrain2016 opened this issue 6 years ago • 9 comments

I install this project with go 1.12.1 on CentOS 7. while lgo install , I got a error:

2019/03/19 07:54:31 Install lgo to /home/jupyter/.lgopath
2019/03/19 07:54:31 Building libstd.so
2019/03/19 07:54:36 Building lgo core package
2019/03/19 07:54:41 Building third-party packages in $GOPATH
2019/03/19 07:54:41 Installing lgo-internal
# github.com/yunabe/lgo/cmd/lgo-internal
type..MO7lsdMr: missing section for relocation target type..FEeY9FdU
type..MO7lsdMr: reloc 8 (R_CALL) to non-elf symbol type..FEeY9FdU (outer=type..FEeY9FdU) 49 (SABIALIAS)
2019/03/19 07:54:48 Failed to build lgo-internal: exit status 2

google provides me no help. Is there something wrong with go 1.12.1?

ryanrain2016 avatar Mar 19 '19 08:03 ryanrain2016

I have the same problem

birbird avatar May 06 '19 15:05 birbird

I also have this issue building lgo with Go 1.12.

$ go version go version go1.12.1 linux/amd64

Russtopia avatar May 08 '19 17:05 Russtopia

same issue met. go version go1.12.5 linux/amd64

bxd avatar May 11 '19 12:05 bxd

same issue go version go1.12.5 linux/amd64

lxzhu avatar May 23 '19 22:05 lxzhu

same issue go version go1.12 linux/amd64

AlexaKuzhel avatar Jun 10 '19 15:06 AlexaKuzhel

same issue go version go1.12 linux/amd64

luoying1105 avatar Jun 14 '19 08:06 luoying1105

Thank you for the reports, all.

I added a section about the current status of this project: https://github.com/yunabe/lgo#disclaimer

Since go1.10, this Go kernel has performance issue due to a performance regression in Go tool chain.

Also, this Go kernel can not be built with go1.12 due to another regression in Go tool chain.

Now, the compiler options this kernel relies on are completely broken and I'm not sure when they will fix the regressions. Unfortunately, they don't plan to fix this in go1.13 as of July 8th 2019. If you are interested in using this kernel, please upvote the bugs. For a while, please use other Go kernels if you want to use the later version of Go with Jupyter notebook.

yunabe avatar Jul 09 '19 13:07 yunabe

I believe this issue was resolved in go1.13. I was able to install straightforwardly on go1.13.5 linux/amd64 and performance seems perfectly acceptable. I don't know how it compares to go1.9 but it is certainly good enough to be productive.

IsaacWolverton avatar Jan 08 '20 01:01 IsaacWolverton