dCore Import Debian Packages to Mountable SCE extensions > dCore x86_64

Linux Kernel Headers

<< < (2/2)

A Guy:
I started doing a build of the dCore-stretch64 kernel and saw a warning go by (I think about Intel microcode). This got me to thinking that perhaps my build environment isn't complete.

Do you have a set of build packages you use when re-compiling the kernel?
I have :

* build-essential
* gcc-multilib
* libc6-dev-i386
Perhaps not all relevant to a rebuild but I was curious what you used.

Jason W:
Thanks for correcting the typos, corrected now in my post.  I was going by memory of the steps. 

Are you using a 64 bit dCore to compile for 32 bit?  I only use 64 bit for 64 bit, and 32 for 32.  Thanks.

A Guy:

--- Quote from: Jason W on July 31, 2019, 05:26:47 PM ---Are you using a 64 bit dCore to compile for 32 bit?  I only use 64 bit for 64 bit, and 32 for 32.  Thanks.

--- End quote ---

That's a good question. The set of files I am using were for general development, so I just listed what I had .
I was just curious what your minimal set is.

A Guy:
I wanted to add, I was running through kernel re-compile and it seemed that after copying the configuration file you had onto .config, the

--- Code: ---make oldconfig
--- End code ---
command seemed to be pulling the .config from another location and over writing it. A diff between the original config file you have and the .config shows that they are pretty different after the build, which shouldn't happen.

I believe the make oldconfig step should be removed , from the procedure.

You see it in many descriptions on how to build a kernel, but then I have also seen it not used.

=== One more thing... linux-4.8.17-patched.tar.txz
What are the patches ? Do you have a patch script?

Tony

Jason W:
Ok, I will look into the make oldconfig thing.


Below is the directory for that kernel and it's patches.  I simply use the linux-4.8.17-patched.tar.xz along with the dCore specific config file. 

Navigation

[0] Message Index

[*] Previous page