Build broken on Fedora 34

[dwillmore]

This is likely user error, but I'm completely new to Teacup and I'm probably holding it wrong.

I'm following the Simple Installation instructions.

I cloned the repo and fired up the config tool. I selected the CNCv3 shield as the board and a Mendel as the printer--I just have a UNO with a CNC shield that I want to work with and there is no printer involved. After saving config.h, I went to build and I get the error:

/usr/lib/gcc/avr/10.2.0/../../../../avr/bin/ld: /home/willmore/src_new/Teacup_Firmware/build/mendel.o (symbol from plugin): in function init':
(.text+0x0): multiple definition of err_codes'; /home/willmore/src_new/Teacup_Firmware/build/intercom.o (symbol from plugin):(.text+0x0): first defined here lto-wrapper: warning: Options to Xassembler do not match: -adhlns=/home/willmore/src_new/Teacup_Firmware/build/display_ssd1306.al, -adhlns=/home/willmore/src_new/Teacup_Firmware/build/delay.al, dropping all -Xassembler and -Wa options. collect2: error: ld returned 1 exit status RC = 1 - Build terminated Link terminated abnormally.

I can't find any references to err_codes in the source, so I'm not sure where it's picking that up. Any advice would be welcome.

[phord]

Hm. err_codes is defined in the intercom.h file, and also in the extruder/intercom.h file. I wonder if your model is including both of them somewhere.

Can you try renaming one of them and see if it helps? The actual type doesn't seem to be used explicitly anywhere, so the name of the enum is unimportant.

[dwillmore]

Thank you for the hint. I commented out one of the copies of the structure and it builds, now. The odd thing is that nothing seems to ever refer to that structure in the executable parts of the code.

…

On Tue, Mar 8, 2022 at 6:50 PM Phil Hord ***@***.***> wrote: Hm. err_codes is defined in the intercom.h file, and also in the extruder/intercom.h file. I wonder if your model is including both of them somewhere. Can you try renaming one of them and see if it helps? The actual type doesn't seem to be used explicitly anywhere, so the name of the enum is unimportant. — Reply to this email directly, view it on GitHub <#330 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPEX7HJPHC2TPHNXJJOF43U67RTBANCNFSM5PUD2MVA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[phord]

That's common in C. The enumerated values are often the only part that matters. In this case, it's ERROR_BAD_CRC.

[dwillmore]

You're correct, sorry, brain needed engaged before mouth.

…

On Tue, Mar 8, 2022 at 7:14 PM Phil Hord ***@***.***> wrote: That's common in C. The enumerated values are often the only part that matters. In this case, it's ERROR_BAD_CRC. — Reply to this email directly, view it on GitHub <#330 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPEX7GT32565JHZQ2LANUTU67UOPANCNFSM5PUD2MVA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>