-
Notifications
You must be signed in to change notification settings - Fork 72
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
MPQUIC installation #42
Comments
Hello, Quentin De Coninck, thanks for your excellent work. I compiled it by using Go 1.19.6, however, I met so many errors.
use of internal package github.com/quic-go/quic-go/internal/ackhandler not allowed
Would you please tell me how to fix these problems? Thanks a lot! |
Hi, did you try the tutorial on this page: https://multipath-quic.org/2017/12/09/artifacts-available.html Section "Starting from the Mininet VM (skip if you downloaded our VM)" Actually you don't need mininet. It works with golang up to version 1.15. |
@snopytas hello, I'm also trying to install the mquic by using Go 1.20.2, but the packet "go get github.com/lucas-clemente/quic-go" is totally different now. Is there any way to successfully run mpquic tests with higher version Go? Thank you in advance! |
Hi @bailiao , I only fully worked with mp-quic using go 1.15. I'm not a go expert, but I know that starting from 1.16 the way how dependencies are installed changed. As mentioned in this pull request [1] there is a patched version of mp-quic at [2] for go 1.17.7. I achieved to run the example program by using go 1.20 with the following commands: The dependencies will be installed and after that the output is [1] #33 |
Thank you, snopytas! I have tried, however, I failed several times. I will try with version 1.15, thanks again! |
Hello, everybody! I want to install the mpquic in real environment, however, I could not install when I executed _go get github.com/lucas-clemente/quic-go and go get -t -u ./... . Does anybody successfully install it? I would very appreciated if someone could tell me how to install it. Thank you so much for your attention and participation.
The text was updated successfully, but these errors were encountered: