search

Klipper3d / klipper

Klipper is a 3d-printer firmware
GNU General Public License v3.0
9.55k stars 5.33k forks source link

Conflict between gcc-pru and gcc-avr #3095

Closed goeland86 closed 4 years ago

goeland86 commented 4 years ago

Installation using the install-beaglebone.sh script doesn't account for gcc-pru and gcc-avr both trying to write the file /usr/lib/libcc1.la.

When installing on beaglebone, we do not need the AVR or ARM toolkits installed (in a single-MCU case) to the best of my understanding. And at present, the attempt to have both gcc-pru and gcc-avr installing fails the installation overall.

This error happens when using a Debian 10.3 base linux image retrofitted to use kernel 4.14 to keep the PRU API consistent with Klipper's expectations.

https://github.com/KevinOConnor/klipper/blob/180f44b8763159d55e1c9c9339849765b093cbb7/scripts/install-beaglebone.sh#L20

goeland86 commented 4 years ago

Just to clarify why this is an issue: Beagleboard's currently supported images for Beaglebone black are based on Debian 10.3, which is where security updates are happening, and in the Replicape's particular case, python 3 versions that will support OctoPrint (i.e. Python 3 > 3.6) are only available in 10.3. If Replicape will keep being supported, it needs to run Klipper on Debian 10.3 - and I don't see any reason it cannot, except for this package conflict during installation at the moment.

klipper-gitissuebot commented 4 years ago

Hi @goeland86,

It did not look like there was a Klipper log file attached to this ticket. The log file has been engineered to answer common questions the Klipper developers have about the software and its environment (software version, hardware type, configuration, event timing, and hundreds of other questions).

Unfortunately, too many people have opened tickets without providing the log. That consumes developer time; time that would be better spent enhancing the software. If this ticket references an event that has occurred while running the software then the Klipper log must be attached to this ticket. Otherwise, this ticket will be automatically closed in a few days.

For information on obtaining the Klipper log file see: https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md

The log can still be attached to this ticket - just add a comment and attach the log to that comment.

Best regards, ~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

goeland86 commented 4 years ago

Here is the klipper install log file, as done by ReFactor using Ansible. klipper_install.log

KevinOConnor commented 4 years ago

This sounds like a bug in the debian gcc-avr package or the beaglebone gcc-pru package - they shouldn't be conflicting on this file. We really do want to be able to install both the gcc-avr and gcc-pru packages because a user may be using multi-mcu or may be using the beaglebone as just a regular host machine.

Is it possible to report this to the beaglebone developers?

-Kevin

goeland86 commented 4 years ago

Yeah I'll submit it to the Debian and beaglebone teams. Just need to find the respective bug report systems they use...

Just wanted to report it here in case anyone is running into this. The Refactor beta image is removing the avr packages installation for now, with a specific note that avr-based boards aren't supported for a multi MCU package at this stage. Since it's a beta image, I'm ok with that, and hopefully it'll be back in place for the actual release if upstream provides a fix.

Also found the cause for the Klipper_pru service needing a manual restart after booting. Will submit a PR for that though.

On Fri, Jul 17, 2020, 04:40 KevinOConnor notifications@github.com wrote:

This sounds like a bug in the debian gcc-avr package or the beaglebone gcc-pru package - they shouldn't be conflicting on this file. We really do want to be able to install both the gcc-avr and gcc-pru packages because a user may be using multi-mcu or may be using the beaglebone as just a regular host machine.

Is it possible to report this to the beaglebone developers?

-Kevin

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/KevinOConnor/klipper/issues/3095#issuecomment-659800997, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEEI46K5Z4YDBCBJZ72STUTR3622VANCNFSM4O2BR2IQ .

github-actions[bot] commented 4 years ago

Hello,

It looks like there hasn't been any recent updates on this Klipper github issue. If you created this issue and no longer consider it open, then please login to github and close the issue. Otherwise, if there is no further activity on this thread then it will be automatically closed in a few days.

Best regards,

~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.