AVR GCC Source Patches for AS5 Beta

Go To Last Post
13 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,
Please find the source patches for the AVR GCC Toolchain released with AVR Studio 5.0 beta I.

http://distribute.atmel.no/tools...

Soundararajan
ATMEL

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

how can we install the .patch files? also is there a list of changes / known issues?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

how can we install the .patch files?

See Bingo's script at the top of the GCC forum. As someone had already found these .patch files before the announcement here Bingo has said he will update the script and build a .deb for Linux users making use of the .patch's (but not for a few days ;-))

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

soundararajan wrote:
Hi all,
Please find the source patches for the AVR GCC Toolchain released with AVR Studio 5.0 beta I.

http://distribute.atmel.no/tools...

Soundararajan
ATMEL

Soundararajan,

There needs to be a link on the Atmel website where AS5 is downloaded that points to the patches for the AVR Toolchain at that other server.

The link needs to be on this page:

http://www.atmel.com/dyn/product...

With instructions on how to get the associated patches.

This is required to conform to the GPLv3 license. (See section 6(d).)

Also, there has already been discussion online where certain patches to avr-libc 1.7.1 will cause the build of avr-libc to fail. These patches should, ideally, be removed from the patch set.

Eric Weddington
Open Source Community Manager
Atmel

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

gyang1127 wrote:
how can we install the .patch files? also is there a list of changes / known issues?

You don't install the patch files. These are not patches to executables.

These are patches to the source code of GNU Binutils, and GCC, and it is required by the GPLv3 license that they be available to the public in case you wish to rebuild and modify the source code of these projects yourselves.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

i looking for tutorial How to rebuild / patch up the AVR GCC Tool chain for Window OS

P.Ashok Kumar

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I don't have enough time now for a full tutorial but can give a brief sketch:
Download the source code
Apply the patches to the source code
Build the executables
Be happy with the result. There may be bugs, but they are now *your* bugs.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

i looking for tutorial How to rebuild / patch up the AVR GCC Tool chain for Window OS

But why would you need to do this for Windows? The whole point is that Atmel already built the toolchain for Windows for you. The real issue was that it was not possible for it to be built for Linux (and Mac OSX) until these patches were published.

So explain why you think YOU need to build it for Windows? If you want a copy just (once and for all) download and install AS5 then simply excise a copy of the \Program Files\Atmel\AVR Studio 5.0\extenstions\Applications\AVR Toolchain directory tree and you now have a windows hosted copy of avr-gcc

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

i looking for tutorial How to rebuild / patch up the AVR GCC Tool chain for Window OS

I know you've been pointed to the WinAVR documentation, that talks about this subject, in the past. What is missing from that description? I'm sure EW would love constructive suggestions for improvement.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Look, guys, who cares why one wants to build the toolchain for Windows? We're not here to try to decipher why, especially when others are easily available.

If the user wants to build the tools on their own, the avr-libc user manual has instructions on how to do that. Not that it's real easy, mind you.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Now I Downloaded the AS5 Beta and copied the tool-chain ok everything fine.

Quote:
the source patches for the AVR GCC Toolchain released with AVR Studio 5.0 beta
Now what i have to do with source patches? so thought learning of Building the tool chain may help me to update Tool_chain.
i am using and know only window so requested for window.

P.Ashok Kumar

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Now what i have to do with source patches? so thought learning of Building the tool chain may help me to update Tool_chain.

It's the other way round. The patches come from the build of AVR Toolchain. You don't have to "do" anything with them because they've already been used.

The fact is that for the avr-gcc, binutils, avr-libc projects you can pull "HEAD" which is the most up to date release version but in each case it will not necessarily have the very latest changes in it. So there are then patches to be applied to those base versions to bring them even further up to date (many developed by Atmel for support of very new AVR models).

So when Atmel built "Toolchain" that is in AS5 then pulled the generic "HEAD" of each project and then applied a set of patches and built the resultant software tree then put the binaries that this produced in the AS5 install package. Which means if you download and install AS5 you have the most up to date avr-gcc/avr-libc/etc. possible. If you just use Windows you need do nothing more and can ignore the .patch files all together.

The issue was that avr-gcc/binutils are published under a license called GPL which makes it a requirement that anyone who uses the resultant binaries MUST be able to rebuild those binaries themselves if they choose. To do that they'd need access to "HEAD" of the trees *AND* the .patch files that were also applied. For almost a month after the release of AS5 Atmel were in violation of that license and did not make the patches they had used available. In this thread they finally announced that they had now made the files public.

All this (on the whole) is of no concern to anyone using AS5 and the AVR Toolchain on a Windows computer as they already have everything built up to date.

The people who were concerned were those of us who use Linux or Mac OSX because without the patches we had no way to build a Linux or Mac based identical copy of the AVR Toolchain in AS5. By publishing these patches Atmel have now opened the possibility for Mac and Linux toolchains to be built that offer the same device support and bug fixes as found in AS5+Toolchain.

If you thought that the patches announced here were something you had to use to update your Windows installed copy of AS5 and "Toolchain" then you have misunderstood. The fact is you already have everything that is delivered by these patches. It's just that the other half of the development world - the ones that Atmel have chosen to ignore - did not until this release (although someone had actually noticed it a couple of days before this thread was created anwyay)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
If you thought that the patches announced here were something you had to use to update your Windows installed copy of AS5 and "Toolchain" then you have misunderstood

Thank you clawson for clearing my misunderstood about the patches.

P.Ashok Kumar