Jakub Jelinek writes:
> Hi!
>
> Here is an updated version which doesn't warn about #include_next.
> Ok for trunk?
>
> 2013-12-10 Jakub Jelinek
>
> * sanitizer_common/Makefile.am (AM_CPPFLAGS): Add
> -isystem $(top_srcdir)/include/system.
> * sanitizer_common/Makefile.in: Reg
Hi!
Here is an updated version which doesn't warn about #include_next.
Ok for trunk?
2013-12-10 Jakub Jelinek
* sanitizer_common/Makefile.am (AM_CPPFLAGS): Add
-isystem $(top_srcdir)/include/system.
* sanitizer_common/Makefile.in: Regenerated.
* include/system/
On Fri, Dec 6, 2013 at 2:04 PM, Jakub Jelinek wrote:
> On Fri, Dec 06, 2013 at 01:52:29PM +0100, Richard Biener wrote:
>> > Note that testing still shows some issues, e.g. because the
>> > kThreadDescriptorSize change has not been applied. But it at least builds
>> > and for many tests works.
>>
On Fri, Dec 06, 2013 at 01:52:29PM +0100, Richard Biener wrote:
> > Note that testing still shows some issues, e.g. because the
> > kThreadDescriptorSize change has not been applied. But it at least builds
> > and for many tests works.
>
> What's wrong with just copying the kernel headers 1:1? I
On Fri, Dec 6, 2013 at 1:43 PM, Jakub Jelinek wrote:
> Hi!
>
> Here is an alternative version of the patch I've posted earlier to allow
> building libsanitizer on 2.6.18-ish kernel headers, this time by adding
> 5 tiny kernel header wrappers.
> The only drawback of this are warnings like:
> ../../
Hi!
Here is an alternative version of the patch I've posted earlier to allow
building libsanitizer on 2.6.18-ish kernel headers, this time by adding
5 tiny kernel header wrappers.
The only drawback of this are warnings like:
../../../../libsanitizer/include/linux/aio_abi.h:2:2: warning: #include_n