aboutsummaryrefslogtreecommitdiff
path: root/packages/gcc/10.3.0/0023-Remove-use-of-include_next-from-c-headers.patch
Commit message (Collapse)AuthorAgeFilesLines
* Run patches thru `manage-packages -P`Alexey Neyman2022-02-111-307/+0
| | | | | | | | This refreshes the line numbers, removes any fuzz (which would make any future forward ports easier) and standardizes the patch/file headers (which makes them easier to read). Signed-off-by: Alexey Neyman <stilor@att.net>
* packages/gcc/libstdc++: #include_next → #includeKeith Packard2021-06-171-0/+307
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>