kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Andreev <andreev@swemel.ru>
To: kernelnewbies@kernelnewbies.org
Subject: Re[3]: internal / external include files
Date: Thu, 25 Jul 2019 08:45:32 +0300	[thread overview]
Message-ID: <5D3941FC.7050608@swemel.ru> (raw)
In-Reply-To: <20190724212053.zynpswlhepi52dhi@viti.kaiser.cx>

Hi, Martin.

The [$KERNEL_ROOT/include/uapi/linux/stddef.h] you are talking about is just a few lines:

| #include <linux/compiler_types.h>
|
| #ifndef __always_inline
| #define __always_inline inline
| #endif

it turns into

| #ifndef __always_inline
| #define __always_inline inline
| #endif

after [make headers_install] installs it into [/usr/include/linux/stddef.h].

Userspace applications shall not use kernel tree directly.

Regards, Konstantin.

Martin Kaiser, 25 jul 2010 00:20 msk:
>
> I called gcc with -I $KERNEL_ROOT/include/uapi. This is the chain of files that were included.
>
> my_app.c
>     $GCC_SYSROOT/usr/include/netinet/in.h
>        ...
>
> and the error is
>
> $KERNEL_ROOT/include/uapi/linux/stddef.h:2:34: fatal error: linux/compiler_types.h: No such file or directory #include <linux/compiler_types.h>
>
> Best regards, Martin

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2019-07-25  5:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24  9:11 internal / external include files Martin Kaiser
2019-07-24  9:21 ` Greg KH
2019-07-24 21:20   ` Martin Kaiser
2019-07-25  5:45     ` Konstantin Andreev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5D3941FC.7050608@swemel.ru \
    --to=andreev@swemel.ru \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).