summaryrefslogtreecommitdiff
path: root/patches/gcc/4.2.2/100-uclibc-conf.patch
AgeCommit message (Collapse)AuthorFilesLines
2015-10-31gcc: Support only the latest branch releases of gccBryan Hundven1-216/+0
This change, as per #222, reduces the number of supported releases of gcc to the latest branch releases. I noticed while doing this work that gcc-4.5.4 was never added, so I moved patches for gcc-4.5.3 to 4.5.4 and updated the bfin-unknown-linux-uclibc example. Also, 120-siginfo.patch was fixed upstream in the 4.5.4 release, so this patch is omitted. I also bumped the avr sample to 4.9.3 from 4.9.2. With the addition of gcc-5.x, the gcc release team now releases the major.minor.0 versions, while updates to the branch are available in svn/git. We'll address that when we get to issue #219. This change just removes CC_GCC_5_1 and moves CC_GCC_5_2 to CC_GCC_5, and removes CC_GCC_5_1_or_later and moves CC_GCC_5_2_or_later to CC_GCC_5_or_later. This is the first of two part changes, as mentioned in #222. This change is slated for release in 1.22.0. The next change will be slated for 1.23.0, and will limit gcc versions to what is on https://gcc.gnu.org under "Release Series and Status", which is currently 4.9.3 and 5.2.0, although I will also support the previous supported version. In this example that would be 4.8.5. Last, but not least, this change also retires AVR32 support. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2008-02-17Robert P. J. DAY says:Yann E. MORIN"1-0/+216
apparently, the patchset for gcc 4.2.1 applies properly to the source for gcc 4.2.2 and gcc 4.2.3. so, if you want, you can simply add support for those last two just by augmenting menuconfig and adding a couple symlinks for those two directories. seems like a cheap way to add a couple new versions.