diff options
| author | Keith Packard <keithp@keithp.com> | 2021-01-24 16:48:42 -0800 |
|---|---|---|
| committer | Keith Packard <keithp@keithp.com> | 2021-06-17 10:30:25 -0700 |
| commit | 83029d75705e029ba17494d4132e1c01294ce85e (patch) | |
| tree | 4816855c96b20f76e23d10fb530e9709dd10a1a7 /packages/gdb/6.8a/0000-dwarf-stack-overflow.patch | |
| parent | 3e259dbaf8a42310a4ee60a0d816bde8551e1be3 (diff) | |
| download | crosstool-ng-83029d75705e029ba17494d4132e1c01294ce85e.tar.gz crosstool-ng-83029d75705e029ba17494d4132e1c01294ce85e.tar.bz2 crosstool-ng-83029d75705e029ba17494d4132e1c01294ce85e.zip | |
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/gdb/6.8a/0000-dwarf-stack-overflow.patch')
0 files changed, 0 insertions, 0 deletions