From: neutrino network <neutrino.network1@gmail.com>
To: noloader@gmail.com
Cc: "Scott J. Crouch" <scottjcrouch@gmail.com>,
kernelnewbies@kernelnewbies.org
Subject: Re: Missing linux-headers
Date: Mon, 10 Oct 2022 14:57:26 +0500 [thread overview]
Message-ID: <CABbRPAXXXk7RjLwFGabW-iQV+GZSONpg_8Od8Ck82UpfrvmZVQ@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8nv-8FO9fagfW+O7xAJ0P3u7b+U=gHXAMS4R=s7+ftGDA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]
On Mon, Oct 10, 2022 at 6:41 AM Jeffrey Walton <noloader@gmail.com> wrote:
> On Sun, Oct 9, 2022 at 2:11 AM neutrino network
> <neutrino.network1@gmail.com> wrote:
> > ...
> > >> If so, you should probably install the kernel development headers
> packaged by your distribution,
> > Trying to install headers with "sudo yum -y install kernel-headers"
> returns that headers are already installed even its removal reinstall the
> old kernel headers
> > Tried also "yum install kernel-headers-$(uname -r) " !
>
> Sadly, that {behavior|misfeature|bug} has been around forever: the
> kernel-headers package does not install kernel headers. Also see
> https://bugzilla.redhat.com/show_bug.cgi?id=1190394 .
>
> You may want the kernel-devel package, instead.
>
> Jeff
>
Thank you all, I set the environment variable "export
C_INCLUDE_PATH=<linux-kernel-source-path>/usr/include/" and the application
can now be compiled.
Cheers
[-- Attachment #1.2: Type: text/html, Size: 1548 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-10-10 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 4:01 Missing linux-headers neutrino network
2022-10-08 6:21 ` Scott J. Crouch
2022-10-09 6:10 ` neutrino network
2022-10-10 1:11 ` Scott J. Crouch
2022-10-10 1:40 ` Jeffrey Walton
2022-10-10 9:57 ` neutrino network [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=CABbRPAXXXk7RjLwFGabW-iQV+GZSONpg_8Od8Ck82UpfrvmZVQ@mail.gmail.com \
--to=neutrino.network1@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=noloader@gmail.com \
--cc=scottjcrouch@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).