-
-
Notifications
You must be signed in to change notification settings - Fork 793
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
dockerfile uses gcc-avr version that no longer exists #6773
Comments
You should be able to remove all the AVR stuff in lines 16-20 from the Dockerfile since we dropped support for AVR stuff in 2.2 anyway. We removed it in 2.3. https://github.com/opentx/opentx/blob/2.3/radio/util/Dockerfile |
found the missing files. Hope it helps. It built fine for me now. Thanks @kilrah |
Did you try removing them as I suggested? If that works it is a better fix. |
I didn't go that route first because I didn't want to remove a feature from a stable version, even if that feature is declared not supported. But I did test building it right now: as expected, this works for me too: "[100%] Built target firmware" :) Thanks! |
Before submitting, search the open issue if there is already a report of the bug
found no open issues for dockerfile
Describe the bug
I try to build latest stable release version 2.2.4 in a supported environment following OpenTX-2.2-Linux-Build-Instructions
This is not possible.
To Reproduce
I installed docker on my opensuse leap 15.1 system (any other source system will do)
Then I downloaded the dockerfile and tried to build the docker image.
This fails after some time
Expected behavior
Image build succeeds.
I already checked: the gcc-avr_4.7.2-2_amd64.deb does not exist (anymore) at http://ftp.de.debian.org/debian/pool/main/g/gcc-avr.
Oldest available version is the 5 year old version 4.8.1.
Since I don't know debian, I don't know where to find older versions.
Since this is my first contact with opentx and the link above warns about inconsistent behavior I hesitate to use other gcc-avr versions.
Do you have a workaround? This should then probably be documented at the link above and dockerfile adapted.
Thank you.
The text was updated successfully, but these errors were encountered: