On 24/01/2019 10.32, Andrei Borzenkov wrote:
On Thu, Jan 24, 2019 at 12:13 PM Carlos E.R. <> wrote:
On 24/01/2019 05.32, Andrei Borzenkov wrote:
22.01.2019 0:53, Carlos E. R. пишет:
On 21/01/2019 22.46, Carlos E. R. wrote:
Hi,
...
So, what should I use instead to get the same result? Perhaps copy /proc/config.gz to /usr/src/linux and expand it?
I did that (to get a .config), and now I get:
Telcontar:/usr/src/linux # echo -e "\n-- scripts --" && make scripts && echo -e "\n-- prepare --" && make prepare && echo -e "\n-- Done good! --"
-- scripts -- scripts/kconfig/conf --silentoldconfig Kconfig ... scripts/mod/modpost.c:26:10: fatal error: ../../include/generated/uapi/linux/suse_version.h: No such file or directory #include "../../include/generated/uapi/linux/suse_version.h" ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
suse_version.h is generated during "make prepare"
Well, it wasn't.
As you can see above, I did run "make prepare".
No, you did not. It failed before "make prepare". If you run it before, we obviously have no way to know it.
I posted the command line I used with the order of commands I used, the same for perhaps a decade: make scripts make prepare Now for some unknown reason it has to be reversed, but the official documentation has not changed. Notice the documentation at "/usr/src/linux/README.SUSE", it says: The first method involves the following steps: (1) Install the kernel-source package. (2) Configure the kernel, see HOW TO CONFIGURE THE KERNEL SOURCES. (3) Create files required for compiling external modules: ``make scripts'' and ``make prepare''. <================================ (4) Compile the module(s) by changing into the module source directory and typing ``make -C $(your_build_dir) M=$(pwd)''. (5) Install the module(s) by typing ``make -C $(your_build_dir) M=$(pwd) modules_install''. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)