Eric Blake wrote:
> But obviously, glibc has some way of marking a header file as a system
> header, so that the use of extensions such as #include_next do not trigger
> gcc -pedantic warnings. Is there a #pragma that glibc uses to do that?
> And should gnulib do the same?
The code that emits thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Reuben Thomas on 8/24/2008 4:47 PM:
>> gnulib cannot avoid the use of #include_next. On non-glibc platforms it
>> would be possible, by use of #include ,
>> but with glibc it is not possible, because glibc itself uses
>> #include_next.
Bu
On Mon, 25 Aug 2008, Bruno Haible wrote:
Reuben Thomas wrote:
it'd need some way for gnulib to turn it off, and
gnulib would then have to use it.
gnulib cannot avoid the use of #include_next. On non-glibc platforms it
would be possible, by use of #include ,
but with glibc it is not possible,
Reuben Thomas wrote:
> it'd need some way for gnulib to turn it off, and
> gnulib would then have to use it.
gnulib cannot avoid the use of #include_next. On non-glibc platforms it
would be possible, by use of #include ,
but with glibc it is not possible, because glibc itself uses #include_next.
On Sun, 24 Aug 2008, James Youngman wrote:
On Sun, Aug 24, 2008 at 10:52 PM, Reuben Thomas <[EMAIL PROTECTED]> wrote:
Sounds interesting, but I can't find it. Have you a pointer to where this
comes from? I can't find it in any obvious place.
It was attached to the email to which you were repl
On Sun, Aug 24, 2008 at 10:52 PM, Reuben Thomas <[EMAIL PROTECTED]> wrote:
> Sounds interesting, but I can't find it. Have you a pointer to where this
> comes from? I can't find it in any obvious place.
It was attached to the email to which you were replying.
James.
On Sun, 24 Aug 2008, Bruno Haible wrote:
Hello,
Reuben Thomas wrote:
I compile my code with -pedantic, because I want it to work with compilers
other than GCC. This means that my compiler output is littered with warnings
about #include_next.
gnulib is clever enough to use #include_next only
On Fri, Aug 15, 2008 at 10:15:52PM -0600, Eric Blake wrote:
> According to Tom G. Christensen on 8/14/2008 9:03 AM:
> > On Wed, Aug 13, 2008 at 08:14:43PM -0600, Eric Blake wrote:
> >> According to Tom G. Christensen on 8/13/2008 2:45 PM:
> >> it looks like c-stack will work with libsigsegv, once w
Hello,
Reuben Thomas wrote:
> I compile my code with -pedantic, because I want it to work with compilers
> other than GCC. This means that my compiler output is littered with warnings
> about #include_next.
gnulib is clever enough to use #include_next only with compilers that support it
(i.e. g
I compile my code with -pedantic, because I want it to work with compilers
other than GCC. This means that my compiler output is littered with warnings
about #include_next. How can I stop this? It's a pain to read through; of
course I can grep out the warnings, but that's that's an annoyance too
Hi,
Alexander V. Lukyanov wrote:
> I'm trying to use wcwith replacement on Solaris 8 and have noticed some
> problems. At first, the test for replacement did not detect the problem and
> thus did not replace the system function (patch for this is attached).
The comment in your diff says:
> +
11 matches
Mail list logo
