On Mon, 21 Oct 2013, Juergen Weigert wrote:
On Oct 19, 13 00:07:01 +0400, Matwey V. Kornilov wrote:
Hi,
In CrossToolchain:avr, I see avr-gcc-* and cross-avr-gcc. What is the difference? What is correct naming? (I suppose the last one).
We wanted to get rid of the 'cross-' prefix at some point. I personally do not care so much about naming, and did not check if this move was ever completed. Probably not.
The original compiler package that I bootstrapped there was cross-avr-gcc version 4.3.3 but newer compilers come from the package avr-gcc-master and are named avr-gcc-436, avr-gcc-453, avr-gcc-462, avr-gcc-47-20111105 -
Why we just don't have cross-avr-gcc48.spec in devel:gcc gcc48 like every other arch does? It is interesting that Factory supplies cross-avr-binutils but not cross-avr-gcc. May I try to push avr-support to devel:gcc?
I once pulled all the cross-avr toolchain from Factory as it was quite broken. (cross-avr-binutils somehow survived in Factory).
We then created several packages in CrossToolchain:avr, but none of them got ever submitted to Factory. Devel:gcc would make a lot of sense, if we go with mainstream gcc. Several years back, I had issues with miscompiled switch statements code size increasements. I'd recommend to double checks these again with gcc-4.8 -- it is definitly worth a try withing devel:gcc
Note that I ripped out the non-suse-glibc target support during hackweek
as it was unused (I mainly wanted to consolidate the various .spec.in
files we have - now down to two). So you have to hack this back in
in a clean way.
Richard.
--
Richard Biener