linux/init.h not found

nononono · 04-30-2023, 10:12 AM

Whatever I'm doing, it returns a fatal error. So far, I have tried loading and reloading kernel files. I checked the directory where it's supposed to be, and the file init.h is there. I also tried to write a full path to the directory, but then it suddenly gave me a fatal error that there is no linux/lists.h or something similar. After including it, it gave me another fatal error and so on, until it demanded compiler_types. I added an include with the full path to compiler_types, but every compilation attempt failed because compiler_types was not found (everything was in the linux directory).

I also tried creating a new Ubuntu virtual machine, but the issue persists. Please help. I am really new to Linux and need to finish my coursework by tomorrow

does it have something to do with my kernel version? (i have the newest by now)

RandomTroll · 04-30-2023, 10:27 AM

What are you doing? I suspect you're trying to build the kernel.

<>-type includes look in 'the standard system directories'. The errors you report sound as though the compiler disagrees with the system about the standard system directories. It's usually a fool's errand to change all the <>-includes to ""-includes: there are too many. Where is linux/init.h?

nononono · 04-30-2023, 10:35 AM

Basically, i tried to change #include <linux/init.h> so it would be
#include </usr/src/linux-headers-5.19.0-41-generic/include/linux/init.h>, but it results in more errors.
I need to make a simple firewall in Linux.

teckk · 04-30-2023, 11:38 AM

https://www.geeksforgeeks.org/c-c-in...with-examples/

pan64 · 04-30-2023, 11:44 AM

I don't understand it. If it is a course you got all the required info to make it. But you did not give us any details, so actually we cannot tell you what went wrong.
Using full path in includes is not really suggested. What kind of course is it at all?
From my side I think you missed a command line option somewhere, or mistyped something, but obviously without details it is just a wild guess.

RandomTroll · 04-30-2023, 10:19 PM

How does one know what directories are looked in?

teckk · 05-01-2023, 08:55 AM

Quote:

How does one know what directories are looked in?

find and locate, or any if the graphical search tools.

Also:

Code:

$(gcc -print-prog-name=cc1plus) -v
$(gcc -print-prog-name=cpp) -v

$(gcc -print-prog-name=cc1) -v

echo "#include <stdio.h>" > t.c; gcc -v t.c; rm t.c

gcc -v -E - < /dev/null

gcc -v -E -xc - < /dev/null

Etc.

RandomTroll · 05-01-2023, 02:44 PM

Quote:

Originally Posted by teckk

find and locate

find what?

Code:

find the include directories

? I didn't ask how to know where they were but to know what they were.
Some of your subsequent answers seem to point the answer.

The last few instances of building the kernel have returned a failure to find asm/byteorder.h for both insn.h and orc_types.h. I replace the <> includes with fully-qualified includes, which works. But there are 527 instances of includes of asm/byteorder.h in the source: why does it fail to find only in thoses 2 instances? I've been building my kernel for more than 20 years - it's just happened in the last 3 versions.