https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c1 Juergen Weigert changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jw@suse.com |kkzhang@suse.com --- Comment #1 from Juergen Weigert 2012-06-19 16:44:29 UTC --- I did not mean to fix this myself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c3 Juergen Weigert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amilcar@kdevelop.org --- Comment #3 from Juergen Weigert 2012-09-11 19:39:06 UTC --- *** Bug 779824 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=779824 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c5 --- Comment #5 from Milan Hejpetr 2012-11-11 20:02:52 UTC --- Created an attachment (id=512770) --> (http://bugzilla.novell.com/attachment.cgi?id=512770) avr-gcc wrapper avr-gcc wrapper -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c7 --- Comment #7 from Milan Hejpetr 2012-11-11 20:11:19 UTC --- Then you can use avr-gcc transparently (from command line, Eclipse etc...). If you need Arduino Sketch, do not use package from OpenSUSE 12.2 repositories - use package from: http://arduino.cc/en/Main/Software -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c9 Volker Kuhlmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |volker3204@paradise.net.nz --- Comment #9 from Volker Kuhlmann 2013-09-05 18:18:42 NZST --- I disagree with this issue being any problem at all. Having to re-login once after installing any AVR package is fine (or having to change PATH manually). You have to rehash your shell path anyway if you work on the command line. A warning to this effect would be good though. My avr-gcc packages fail here as well, the script e.g. run-avr-gcc-463 is required when installing multiple compiler versions. One solution is to add /etc/profile.d/avr-gcc.{c,}sh, but that would have to be done by the first package installed; or the files are created by rpm postinstall script. Much better would be to actually follow Linux guidelines and install the packages properly into /usr. I tried, and it's not that difficult, but avr-libc, avr-binutils and avr-gcc have to all be moved at the same time because they must all be in the same place (otherwise things get very messy). I was hoping whoever looks at the AVR repo might get that started at least for oS12.2. At the same time, that braindead "cross-" prefix should be dropped from the package names. Apart from making the name longer it carries zero information. The fact that there is an "avr-" prefix already makes it all plenty clear. Those needing more should not be running cross-compilers... ;-))) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c11 Volker Kuhlmann changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Other Version|Beta 1 |Final AssignedTo|max@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 12.2 |openSUSE 12.3 Target Milestone|--- |Final --- Comment #11 from Volker Kuhlmann 2013-09-05 21:14:44 NZST --- Changing to openSUSE 12.3 final. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c13 --- Comment #13 from Reinhard Max 2013-09-05 13:12:49 CEST --- AFAIK the package in the OSS repo (I suppose you mean Factory or some released version here) is getting built as a subpackage of the regular binutils, which are all located under /usr. I think we should go with that version, because it means we don't have to maintain binutils in the avr repo ourselves. Maybe the same could be done with gcc, but my experience with gcc packaging is limited. BTW, calling people jokers because they made a mistake isn't helpful, but asside from that your help is appreciated. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c15 Volker Kuhlmann changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #15 from Volker Kuhlmann 2013-09-06 01:03:58 NZST --- Sorry for the joker, but I had to laugh! And I hadn't noticed that it seems to be derived from the normal binutils, plus I was getting frustrated, because after having put a lot of effort into this some while back nothing seemed to be happening in the forward direction. Looking at the package source, the avr-binutils in the OSS repo has a large number of patches applied by SUSE, with at least 2 being specifically for AVR. Otherwise it seems to be the standard x86/x64_64 package source. If someone moved forward and also compiled an AVR version from that, splendid! Less to maintain twice. However avr-libc and avr-gcc must move installation prefix with it, because those 3 packages are not really independent. The binutils in the AVR repo is from vanilla source. Yes the AVR version just uses different compile options than the x86 version, same as for gcc. I mean these repos: http://download.opensuse.org/distribution/12.3/repo/oss/ http://download.opensuse.org/repositories/CrossToolchain:/avr/openSUSE_12.3/ I already did the work of compiling gcc for /usr a long time ago, but had to stop when I found that it can't be installed in a different place than the corresponding binutils, and in the case of AVR, also libc. It's a matter of changing a define in the spec. Jürgen I was never advocating to merge the avr-gcc source package with the gcc (for x86 ...) one, too much trouble, and not at all necessary. Call the package avr-gcc, but change the install-prefix to /usr. Do the same for everything else in the AVR repo. It is of course fine to keep the repo. As for gcc versions, the reason beginners are stuck with 4.3.3 is that the Arduino people are stuck with it, because they're no compiler people and don't want to touch it, or so I've read. I don't know whether Jörg Wunsch is really so set on 4.3.3. In any case the AVR gcc target is maintained by Johann, and he feeds it into the upstream gcc sources. A long time ago he clearly recommended 4.7 simply because it has the most bug fixes and the best optimisations. I haven't checked whether the 4.3.3 int he AVR repo is vanilla, but I really doubt Johann has any interest whatsoever into backporting, he fixes thigns in the current versions and can't keep up there as it is. I haven't found a real reason for 4.3.3 yet other than it being the reference from the arduino IDE. Because I found avr-gcc 4.3.3 unsatisfactory from my point of view I wanted to test the other versions in comparison, so I made this elaborate spec file where I just need to change some numbers to compile a different version. And I definitely wanted to test LTO. Johann says it's not really recommended for AVR, but I found it works for my app. I have just compiled with 4.8.1, and with LTO code size is down almost 10% - but I haven't run it yet. The 4.6.4 and 4.7.3 linker bombs with LTO on my arduino app (but worked fine with binutils-2.19), so it's an option to look at if it works. And now the really good news: all my gcc packages can be installed in parallel! So keep 4.3.3 in the package named avr-gcc. The other versions have different package names. Package naming policy is to call a package avr-gcc when the main component in it is called avr-gcc, or so I understand. Calling it something else is very irritating, to put it politely. You don't want to knwo how many times I've been swearing tonight because rpm -q avr-binutils didn't do. All the programs are called avr-XXX. The same goes for cross-arm-gcc. I couldn't care less about historic when it's a PITA each time I use it today. Fix all of them and you have consistency again... I have updated the spec files and the run script I added, I'll put them up tomorrow after some sleep. I stopped using 4.3.3 years ago, the arduino IDE works fine with the other versiosn too, if one uses my run script - though the newer IDEs have their own compiler integrated (binary from arduino.cc). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c16 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rguenther@suse.com |jw@suse.com --- Comment #16 from Richard Biener 2013-09-06 09:40:08 UTC --- avr-gcc is not maintained by me -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c18 --- Comment #18 from Juergen Weigert 2013-09-09 14:05:23 UTC --- Richard, yes we use --target=avr, but last time I checked, it failed to configure '/usr/bin/avr-as', it just configured 'as', relying on the search patch to sort it out. My wild guess (combining what Volker found out above) is: it does that, when /usr/bin/avr-as is not there at compile time. Plausibly could have happend due to avr-binutils installing under /opt. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c20 --- Comment #20 from Volker Kuhlmann 2013-09-13 12:42:06 NZST --- Yes, no-one wants to do any work :-) I am working on it. My plan is to create rpms for /usr that work, using the avr-binutils created and maintained by mainstream x86. Compiling gcc for /usr is a bit of a bummer, there are many inter-depencies, but I think I have managed. The avr-libc spec is buggy. So are my previous avr-gcc specs, the move to /usr was never quite finished. A problem is that there is no other cross compiler to look at. Suse doesn't even have one for ARM - all what's on OBS is home stuff, which I think is pretty poor. The armv7hl-gcc47 icecream backend, while useful for its purpose, doesn't really cut it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c22 Juergen Weigert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |duwe@suse.com, | |matwey.kornilov@gmail.com --- Comment #22 from Juergen Weigert 2013-10-23 08:46:11 UTC --- Thank you Volker! I am adding Matew and Torsten, who also digged into avr-gcc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=767294 https://bugzilla.novell.com/show_bug.cgi?id=767294#c24 --- Comment #24 from Volker Kuhlmann 2013-11-28 08:31:55 NZDT --- Apologies for not having gone back to this, it's still on my todo list (still to look at Rainhard's efforts too). I can not speak for SLE-anything, I don't have/use it. I never found the wrightflyer instructions or scripts to be of any use since I have been building avr-gcc (about 2 years now), and I find references consisting of no more than some forum handle name to be a bit insufficient. Dropping multiple avr-gcc versions is a bad idea. For starters I have put a LOT of effort into it :-), but there will always be the need to try new versions or to verify code generation with multiple gcc versions. How are you going to find out if 4.8 is really that good unless you can compare? It is still heavily dependent on the actual program being compiled. I have tried with 2-3 of mine, where it always came out top, sometimes by a very significant margin. There is another problem too I discovered recently: some of the Arduino source code on the Internet is written for 4.3.3 only because of its timing, and it falls over very neatly in a progressive way with increasing gcc versions producing faster code (WS2811-based LED chains - the adafruit version is programmed properly, FastSPI_LED2 is not). So IMHO we need to keep 4.3 around for some time to come (current Arduino 1.0.5 uses 4.3.2). It's also needed as the first step to find out whether a problem is due to a compiler version difference or something else. I am not expecting the official IDE to change gcc version for some years, there is not enough incentive to do that for its creators (keeping the target audience in mind). But do delete avr-gcc-47-20111105 immediately, it's a 4.7 pre-release that was the newest 4.7 available at the time I started testing gcc versions. My plan is to have the latest 4.x available, which trivially drops out of the spec file by changing some numbers. If general opinion is that I'm the only one needing that I'm happy to build these just for myself at home. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.