-
Notifications
You must be signed in to change notification settings - Fork 455
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
Problem to compil Codec2/FreeDV #1741
Comments
I guess the commit 76a20416d715ee06f8b36a9953506876689a3bd2 has been squashed. Sticking to it was probably due to a specific issue and it may not be longer valid. Just try without "git reset --hard ..." Note: in Docker we rather stick to a tag |
It appears that all tags have been romoved:
|
Only 1.2.0 tag available in that repo: https://github.com/drowe67/codec2/tags Unless we switch to codec-dev repo: https://github.com/drowe67/codec2-dev/tags See note here: https://github.com/drowe67/codec2/releases external/CMakeLists.txt uses this tag as well. |
That was only 2 days ago. |
Wiki updated |
Looks like a similar change needed in cmake/ci/build_codec2.sh - I think that's why the docker build is failing |
Nope, that's not write. Looks like it's the docker script that needs changing: https://github.com/f4exb/sdrangel-docker/blob/master/sdrangel/Dockerfile |
I have a problem to compil Codec2/FreeDV, I try some times
tutu@ccccccccccc:/opt/build$ git clone https://github.com/drowe67/codec2.git
Clonage dans 'codec2'...
remote: Enumerating objects: 1143, done.
remote: Counting objects: 100% (1143/1143), done.
remote: Compressing objects: 100% (810/810), done.
remote: Total 1143 (delta 413), reused 1051 (delta 324), pack-reused 0
Réception d'objets: 100% (1143/1143), 15.24 Mio | 3.41 Mio/s, fait.
Résolution des deltas: 100% (413/413), fait.
tutu@tcccccccc:/opt/build$ cd codec2
tutu@tcccccccc:/opt/build/codec2$ git reset --hard 76a20416d715ee06f8b36a9953506876689a3bd2
fatal: Impossible d'analyser l'objet '76a20416d715ee06f8b36a9953506876689a3bd2'.
The text was updated successfully, but these errors were encountered: