Broken install with go 1.16: github.com/SRI-CSL/gllvm/cmd/gclang++: malformed import path "github.com/SRI-CSL/gllvm/cmd/gclang++": invalid char '+'

[qtcdxxyuc]

malformed import path "gllvm/cmd/gclang++": invalid char '+'
go get gclang and other is succeed.

[ianamason]

I think the way I install it is described in the README.md

go get github.com/SRI-CSL/gllvm/cmd/...

Which works fine for me.

[ianamason]

Maybe this is a real problem, will have to look into it.

[ianamason]

This appears to be a problem cause by the latest go.

go 1.15.8 -> 1.16

I can now reproduce it:

CSL-CAS7352:STITCHES_Inputs e27658$ go get github.com/SRI-CSL/gllvm/cmd/...
go: downloading github.com/SRI-CSL/gllvm v1.3.0
github.com/SRI-CSL/gllvm/cmd/gclang++: malformed import path "github.com/SRI-CSL/gllvm/cmd/gclang++": invalid char '+'
CSL-CAS7352:STITCHES_Inputs e27658$

[ianamason]

OK so the new go module system appears to have a draconian view of what things can be named.
It does not allow executables to be called things like g++ or gclang++ or clang++, but does
allow things like g--, gclang--, and clang--. Strange. Seems
a bit monocultural to me. Anyway I have filed an issue but I am not holding my breath. We shall see.

In the meantime the work around appear to be:

GO111MODULE=off go get github.com/SRI-CSL/gllvm/cmd/...

If all else fails, there might be a rename in gllvm's future.

[ianamason]

Think this saga is over. Though at some stage I need to update the README.