summaryrefslogtreecommitdiff
path: root/packages/picolibc
diff options
context:
space:
mode:
authorKeith Packard <keithp@keithp.com>2021-01-25 00:48:42 (GMT)
committerKeith Packard <keithp@keithp.com>2021-06-17 17:30:25 (GMT)
commit83029d75705e029ba17494d4132e1c01294ce85e (patch)
tree4816855c96b20f76e23d10fb530e9709dd10a1a7 /packages/picolibc
parent3e259dbaf8a42310a4ee60a0d816bde8551e1be3 (diff)
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>
Diffstat (limited to 'packages/picolibc')
0 files changed, 0 insertions, 0 deletions