Bug#798955: [PATCH] libstdc++: don't use #include_next in c_global headers

On Mon, 20 Apr 2020, Helmut Grohne wrote: Now you are probably going to say that "-isystem /usr/include" is a bad idea and that you shouldn't do that. I'm inclined to agree. This isn't a problem just yet. Debian wants to move /usr/include/stdlib.h to /usr/include//stdlib.h. After that move, the

Bug#798955: [PATCH] libstdc++: don't use #include_next in c_global headers

The and headers need their counter parts and from the libc respectively, but libstdc++ wraps these headers. Now and include these headers using $ echo '#include ' | g++ -x c++ -E - -isystem /usr/include >/dev/null In file included from :1: /usr/include/c++/9/cstdlib:75:15: fatal error: stdli

Bug#910685: glibc: please support DPKG_ROOT

Hi Aurelien, On Tue, Apr 14, 2020 at 05:49:38PM +0200, Helmut Grohne wrote: > Yes, please. Is there anything blocking this? Without support in glibc, > moving forward is a little difficult. Can you include it soonish? I pinged Aurelien on IRC about this. Let me summarize your answer here: * The

Bug#954230: In a sticky directory root cannot write to files owned by normal users

Sounds like protected_regular from https://www.kernel.org/doc/Documentation/sysctl/fs.txt ttfn/rjk