Keith Packard 83029d7570 packages/gcc/libstdc++: #include_next → #include ... Some of the installed libstdc++ header files use '#include_next' to work around toolchain oddities that might cause loops in the compiler. However, these also cause mistakes in locating header files when there are multiple C libraries installed as '#include_next' often ends up finding default C library header files. It doesn't seem like this patch could be accepted upstream; there's a long discussion about the use of include_next in these headers which I cannot fully understand. Signed-off-by: Keith Packard <keithp@keithp.com>		2021-06-17 10:30:25 -07:00
..
4.8.5	Run all patches through renumbering and update	2017-12-02 12:44:39 -08:00
4.9.4	Experimental: Add support for the Texas Instruments C6X (TMS320C6000 series) DSPs	2020-05-20 21:16:14 -04:00
5.5.0	Fix build with ISL 0.20	2018-09-25 17:22:34 -07:00
6.5.0	Import gcc 6.5.0	2018-11-07 23:46:35 -08:00
7.5.0	Version updates	2019-12-25 18:30:23 -08:00
8.4.0	gcc: Remove nested 8.3.0 directory	2020-05-01 15:27:50 +12:00
9.3.0	Update to GCC 9.x to latest release 9.3.0	2020-08-27 11:35:59 +02:00
10.3.0	packages/gcc/libstdc++: #include_next → #include	2021-06-17 10:30:25 -07:00
11.1.0	packages/gcc/libstdc++: #include_next → #include	2021-06-17 10:30:25 -07:00
package.desc	packages: gcc: Add missing milestones	2021-06-07 18:54:58 +09:00