-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Windows: makefile doesn't understand path quirk #2833
Labels
Comments
ghost
mentioned this issue
Jun 13, 2016
ghost
added
kind/bug
A bug in existing code (including security flaws)
topic/windows
Windows specific
regression
topic/tools
Topic tools
and removed
kind/bug
A bug in existing code (including security flaws)
labels
Jun 13, 2016
ghost
mentioned this issue
Jun 17, 2016
ghost
pushed a commit
that referenced
this issue
Jun 17, 2016
This reverts commit ff75bc0, which broke building on windows. See #2833. License: MIT Signed-off-by: Lars Gierth <[email protected]>
kevina
pushed a commit
to ipfs-filestore/go-ipfs
that referenced
this issue
Jun 20, 2016
This reverts commit ff75bc0, which broke building on windows. See ipfs#2833. License: MIT Signed-off-by: Lars Gierth <[email protected]>
It was reverted, should we close it? |
I would say yes, but a separate issue should probably be opened for multiple GOPATH paths if that's still desired. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Previously I have used
make
from the msys2 project inside of a native Windows command line shell to build IPFS, pull #2808 seems to have broken my ability to build this way. This is more than likely do to the way msys and cygwin convert Windows paths i.e. C:\tmp -> /c/tmp.Within an msys2 shell I can build again just fine after setting up Go paths, or installing a second copy of Go inside of the msys environment.
I'm not sure how many people this effects but I don't think it's too uncommon for people to use the native shell and natively installed version of Go if they can.
The text was updated successfully, but these errors were encountered: