Closed nochiel closed 2 years ago
cc @bcmills @jayconrod @matloob
@nochiel the original title had "[Possible regression]". Did you mean that it worked before for some earlier Go release, but not with Go 1.16.4? Thanks.
@nochiel the original title had "[Possible regression]". Did you mean that it worked before for some earlier Go release, but not with Go 1.16.4? Thanks.
As far as I am aware it has never worked. However #18468 was closed, apparently fixed. It's not entirely clear to me if the issues are related or if that fix was supposed to fix the issue. This was why I labelled it as a possible regression, in the event that it was indeed fixed.
No, that's a issue of git itself.
Windows user should set git by git config --system core.longpaths true
Ref: https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows
On Tue, 20 Jul 2021 at 06:46, Meng Zhuo @.***> wrote:
No, that's a issue of git itself. Windows user should set git by git config --system core.longpaths true Ref: https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows
Thank you for the tip. But did you actually test compiling go-libtor on Windows with this setting? It still doesn't work on my machine.
The indicated platform is Windows
which is not mentioned as supported in the README of the go-libtor
:
The library is currently supported on:
- Linux amd64, 386, arm64 and arm; both with libc and musl.
- Android amd64, 386, arm64 and arm; specifically via gomobile.
The reported command seems to report the relevant failure on WIndows 20H2
:
package github.com/ipsn/go-libtor
imports github.com/ipsn/go-libtor/libtor: build constraints exclude all Go files in %GOPATH%\pkg\mod\github.com\ipsn\go-libtor@v1.0.380\libtor
Change https://go.dev/cl/427015 mentions this issue: cmd/go: support long commands in asm and cgo
Related: https://github.com/golang/go/issues/18468
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
go get -u -v -x github.com/ipsn/go-libtor
What did you expect to see?
Successful compiliaton.
What did you see instead?
go get -u -v -x github.com/ipsn/go-libtor
Output