Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1167649 > unrolled thread

Re: UAPI headers including non-UAPI headers by accident?

Started by"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
First post2015-06-18 10:00 +0200
Last post2015-06-18 10:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: UAPI headers including non-UAPI headers by accident? "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> - 2015-06-18 10:00 +0200

#1167649 — Re: UAPI headers including non-UAPI headers by accident?

From"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Date2015-06-18 10:00 +0200
SubjectRe: UAPI headers including non-UAPI headers by accident?
Message-ID<pCCTU-28V-17@gated-at.bofh.it>
[CC += David]

On 2 June 2015 at 18:36, Andy Lutomirski <luto@kernel.org> wrote:
> include/uapi/linux/signal.h starts with:
>
> #ifndef _UAPI_LINUX_SIGNAL_H
> #define _UAPI_LINUX_SIGNAL_H
>
> #include <asm/signal.h>
> #include <asm/siginfo.h>
>
> This causes it to include <asm/signal.h>, which is not the same thing
> as <uapi/asm/signal.h>.  Changing that will break userspace use of
> this header, though, as the uapi/ won't get removed.
>
> What's the correct fix?  This is causing trouble with a UML build for me.

Perhaps David has some insight, since he architected the original UAPI split.

Cheers,

Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web