Bug 1043844

Summary:	Arduino has specific version requirements for avr-gcc
Product:	[Fedora] Fedora	Reporter:	Neil Darlow <neil>
Component:	arduino	Assignee:	Peter Oliver <mavit>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	bruce, giallu, mavit, neil, tchollingsworth
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 19:41:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Neil Darlow 2013-12-17 10:40:06 UTC

Description of problem:
fedora's packaging of arduino uses the repository-provided avr-gcc and avr-binutils. It appears that versions of these tools after avr-gcc-2.3.4 (which the main arduino.cc site bundles with its downloads) cause broken code to be generated.

Version-Release number of selected component (if applicable):
arduino-1.0.5

How reproducible:
Every time.

Steps to Reproduce:
1. Compile RepRap Marlin firmware (GitHub Marlin-Marlin_v1 branch) on fedora with avr-gcc-2.7.3-0.1 or avr-gcc-2.8.1-1
2. Attempt to run the generated code and observe that it crashes
3. Compile the same firmware with the arduino.cc Linux tarball (avr-gcc-2.3.4) or on Windows (using same avr-gcc version) and the generated code works.

Actual results:
For some reason the code generated with the fedora-packaged tools is smaller than that produced by the arduino.cc tarball and Windows installer (which both produce identically sized binary code). The fedora-package produced code, when run on a 3D printer, quickly crashes. The arduino.cc provided toolchain produced code executes normally.

Expected results:
fedora's packaging of arduino and avr-gcc should produce identical binaries to that produced by the arduino.cc downloads.

Additional info:
arduino.cc now bundle the avr toolchain and required java libraries because of this type of problem. They are currently using avr-gcc-2.3.4.

Comment 1 Neil Darlow 2013-12-17 20:52:52 UTC

Excuse my stupidity. I have versions incorrect here. They should be:

avr-gcc-2.3.4 --> avr-gcc-4.3.2
avr-gcc-2.7.3 --> avr-gcc-4.7.3
avr-gcc-2.8.1 --> avr-gcc-4.8.1

Where I got the major version 2 from I do not know. It should, of course, be 4.

Comment 2 Peter Oliver 2013-12-17 23:23:14 UTC

If the Marlin code doesn't compile with a particular version of the AVR toolchain then I guess that's probably indicative of either a bug in the toolchain or a bug in Marlin.

Pragmatically, Arduino ship a known version of the toolchain to work around such issues, but in Fedora we don't want to have lots of special versions of everything so we don't do that.

I don't have a RepRap or an Arduino Mega 2560 to test against, but I notice that compiling the Marlin code in Fedora's Arduino issues a mostly-different set of warnings to Arduino's Arduino.

Could you try reporting this to the Marlin developers?  I think they're probably best-placed to track down the problem.

Comment 3 Neil Darlow 2013-12-18 17:24:12 UTC

I will try but the RepRap firmware community lags behind in respect of development tool versions. The state of the art there appears to be arduino-1.0.1 or earlier (0023?) and I doubt that the code is up to modern gcc-4.8.x standards compliance.

Things are hindered by the fact that the build process is obscured by Arduino itself so being able to tweak compiler and linker options isn't possible for the average user.

Failing any response from the Marlin developers on this, I guess I will have to investigate a Makefile-based build process or do what I am presently doing and build all my firmware under Windows. Not a solution I prefer.

Comment 4 Fedora End Of Life 2015-01-09 20:53:09 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-02-17 19:41:04 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.