I was just trying to track down why my modules started giving weird
errors on rawhide, like:
error: "LINUX_VERSION_CODE" is not defined [-Werror=undef]
error: "KERNEL_VERSION" is not defined [-Werror=undef]
error: missing binary operator before token "("
It seems that "include/linux/version.h" has moved now to a different
path, "include/generated/uapi/linux/version.h". This should be
harmless, as the new path is added with -I too.
However, kernel.spec does this:
> # Make sure the Makefile and version.h have a matching timestamp so that
> # external modules can be built
> touch -r $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/Makefile $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include/linux/version.h
And since -Iinclude comes before -Iinclude/generated/uapi, then my
"#include <linux/version.h>" picks up the touched-empty file. :(
So I suggest this touch command needs to be updated to the generated
path, and perhaps also give it a -c to avoid ever creating a file.
Resending my mail from about a month ago. Any thoughts about enabling
these two options?
----- Forwarded message from Adrian Reber <adrian(a)lisas.de> -----
Date: Tue, 21 Aug 2012 15:31:02 +0200
From: Adrian Reber <adrian(a)lisas.de>
Subject: enable kernel options for criu
Now Checkpoint/Restart in Userspace has released the first version of
their user-space tools I want to ask if it is possible to enable a few
kernel configuration options to use criu? I have prepared a package for
crtools but not yet submitted. As long as the kernel support is not
enabled is does not make much sense.
Following additional options (according to http://criu.org/CR_tools)
which depends on
Any plans on enabling these options? Any chance these options can be
----- End forwarded message -----
I'm Vipin from Computer Science & Engineering background, IIT-BHU. I worked
for a Telecommunication company CDOT India, as a Research Engineer, for
three years. More about me -
IRC handle : _love_hurts_
Skills : auto-tools, C/C++, gdb, RPM packaging, Documentation, Software
development in SunOS
Interested In : kernel development
I can work for around 10 hrs a week. And if I get work related to
Datastructures, Algorithms, C/C++, Networking..then I can work up to 20 hrs
a week :).