Continue custom kernel creation and not start over again from square oneHow to compile and install custom mainline kernelUpstart, one job definition to start and one to stopWhy choose a low latency kernel over a generic or realtime one?Running the Ubuntu Kernel and OS on custom processorKernel driver not installed (rc=-1908) — Againapt asks to upgrade same package over and over again
Would it have been possible to re-fuel the planes in the air?
Is it ethical to apply for a short-term grant with a partner/spouse/girlfriend?
How Much Efficiency is Lost in a Gear Train
As a DM, what are important changes to the play caused by Detect Magic no longer being a cantrip in 5e?
Expressing the Riemann Zeta function in terms of GCD and LCM
Does Dangerous Sorcery apply to cantrips?
Were ancient languages as sophisticated as modern languages?
Senate Impeachment rule change?
How can I get 2 characters to bond while standing alternate watches?
What would have been the typical drinks for a US farmer in the late 18th/early 19th century?
Why there isn't public transport on Christmas Day in the UK
How do you draw a path on a parametric sphere?
Change cone width
Could earthquake cancellation work?
Approximation of homeomorphism by diffeomorphism
What does “critical but stable” mean?
Undercooked areas in chicken breast even though thermometer reads 165 degrees in thickest part
Modeling in pure math
How are concentration checks calculated when at low HP with Death Ward?
Has a remote rogue DNS client managed to slip through the first iptables rule of a Linux DNS server?
Is one spouse responsible if other failed to file taxes
Is there a difference between LASSO regularisation and LASSO penalisation?
Which floor is the Hogwarts Library on?
How to prevent humanity from using alien spaceships and technology exclusively?
Continue custom kernel creation and not start over again from square one
How to compile and install custom mainline kernelUpstart, one job definition to start and one to stopWhy choose a low latency kernel over a generic or realtime one?Running the Ubuntu Kernel and OS on custom processorKernel driver not installed (rc=-1908) — Againapt asks to upgrade same package over and over again
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
Task:
Create a custom Ubuntu kernel from git sources (in my case hwe-branch).
Short summary:
I want to fix a error reported by the build scripts and then repeat only the last compilation/packaging step that failed when compiling a custom kernel.
Longer problem description:
I want to know if it is possible to continue with custom kernel creation without having to build/compile everything from scratch over and over again. I understand so far, that (at least for Xenial 16.04) there are some makefiles in ./debian/rules.de which do all the kernel compilation work.
However, after finding out why a certain compilation/packaging step failed and then correcting the issue (e.g. wrong proxy configuration and therefore installing of spl-dkms from an online repo failed) I want to continue after the last successful step.
I tried to identify the responsible parts in the makefile (in most cases it was ./xenial/debian/rules.d/2-binary-arch.mk) and tried to comment out the actual compilation which takes the most time (the part beginning with # Do the actual build, including image and modules).
Unfortunately, this strategy doesn't seem to work. Building the kernel always fails later on for reasons that are beyond my Linux kernel creation skills, often requesting a run of make mrproper which also erases the ./debian subdir containing the build scripts and thus making the entire build environment dysfunctional.
Is it possible to avoid repeating the compilation of the whole kernel because of minor issues that are easy to fix?
kernel scripts compiling makefile
add a comment
|
Task:
Create a custom Ubuntu kernel from git sources (in my case hwe-branch).
Short summary:
I want to fix a error reported by the build scripts and then repeat only the last compilation/packaging step that failed when compiling a custom kernel.
Longer problem description:
I want to know if it is possible to continue with custom kernel creation without having to build/compile everything from scratch over and over again. I understand so far, that (at least for Xenial 16.04) there are some makefiles in ./debian/rules.de which do all the kernel compilation work.
However, after finding out why a certain compilation/packaging step failed and then correcting the issue (e.g. wrong proxy configuration and therefore installing of spl-dkms from an online repo failed) I want to continue after the last successful step.
I tried to identify the responsible parts in the makefile (in most cases it was ./xenial/debian/rules.d/2-binary-arch.mk) and tried to comment out the actual compilation which takes the most time (the part beginning with # Do the actual build, including image and modules).
Unfortunately, this strategy doesn't seem to work. Building the kernel always fails later on for reasons that are beyond my Linux kernel creation skills, often requesting a run of make mrproper which also erases the ./debian subdir containing the build scripts and thus making the entire build environment dysfunctional.
Is it possible to avoid repeating the compilation of the whole kernel because of minor issues that are easy to fix?
kernel scripts compiling makefile
It is possible to do an incremental compile, but I have never figured out how for the Ubuntu method. For the mainline kernel, I do incremental compiles all the time.
– Doug Smythies
Oct 2 at 14:28
Thank you. But using the Ubuntu config files on the mainline kernel does not give me the Ubuntu kernel, correct? My understanding was that there are Debian/Ubuntu patches applied to mainline kernel before compiling.
– llvs
Oct 7 at 7:14
Yes, correct, you do not get the Ubuntu kernel. My point was that incremental compiles are possible. By the way, I use mainline kernels on my 16.04 server all the time.
– Doug Smythies
Oct 7 at 15:04
add a comment
|
Task:
Create a custom Ubuntu kernel from git sources (in my case hwe-branch).
Short summary:
I want to fix a error reported by the build scripts and then repeat only the last compilation/packaging step that failed when compiling a custom kernel.
Longer problem description:
I want to know if it is possible to continue with custom kernel creation without having to build/compile everything from scratch over and over again. I understand so far, that (at least for Xenial 16.04) there are some makefiles in ./debian/rules.de which do all the kernel compilation work.
However, after finding out why a certain compilation/packaging step failed and then correcting the issue (e.g. wrong proxy configuration and therefore installing of spl-dkms from an online repo failed) I want to continue after the last successful step.
I tried to identify the responsible parts in the makefile (in most cases it was ./xenial/debian/rules.d/2-binary-arch.mk) and tried to comment out the actual compilation which takes the most time (the part beginning with # Do the actual build, including image and modules).
Unfortunately, this strategy doesn't seem to work. Building the kernel always fails later on for reasons that are beyond my Linux kernel creation skills, often requesting a run of make mrproper which also erases the ./debian subdir containing the build scripts and thus making the entire build environment dysfunctional.
Is it possible to avoid repeating the compilation of the whole kernel because of minor issues that are easy to fix?
kernel scripts compiling makefile
Task:
Create a custom Ubuntu kernel from git sources (in my case hwe-branch).
Short summary:
I want to fix a error reported by the build scripts and then repeat only the last compilation/packaging step that failed when compiling a custom kernel.
Longer problem description:
I want to know if it is possible to continue with custom kernel creation without having to build/compile everything from scratch over and over again. I understand so far, that (at least for Xenial 16.04) there are some makefiles in ./debian/rules.de which do all the kernel compilation work.
However, after finding out why a certain compilation/packaging step failed and then correcting the issue (e.g. wrong proxy configuration and therefore installing of spl-dkms from an online repo failed) I want to continue after the last successful step.
I tried to identify the responsible parts in the makefile (in most cases it was ./xenial/debian/rules.d/2-binary-arch.mk) and tried to comment out the actual compilation which takes the most time (the part beginning with # Do the actual build, including image and modules).
Unfortunately, this strategy doesn't seem to work. Building the kernel always fails later on for reasons that are beyond my Linux kernel creation skills, often requesting a run of make mrproper which also erases the ./debian subdir containing the build scripts and thus making the entire build environment dysfunctional.
Is it possible to avoid repeating the compilation of the whole kernel because of minor issues that are easy to fix?
kernel scripts compiling makefile
kernel scripts compiling makefile
asked Oct 2 at 14:07
llvsllvs
12 bronze badges
12 bronze badges
It is possible to do an incremental compile, but I have never figured out how for the Ubuntu method. For the mainline kernel, I do incremental compiles all the time.
– Doug Smythies
Oct 2 at 14:28
Thank you. But using the Ubuntu config files on the mainline kernel does not give me the Ubuntu kernel, correct? My understanding was that there are Debian/Ubuntu patches applied to mainline kernel before compiling.
– llvs
Oct 7 at 7:14
Yes, correct, you do not get the Ubuntu kernel. My point was that incremental compiles are possible. By the way, I use mainline kernels on my 16.04 server all the time.
– Doug Smythies
Oct 7 at 15:04
add a comment
|
It is possible to do an incremental compile, but I have never figured out how for the Ubuntu method. For the mainline kernel, I do incremental compiles all the time.
– Doug Smythies
Oct 2 at 14:28
Thank you. But using the Ubuntu config files on the mainline kernel does not give me the Ubuntu kernel, correct? My understanding was that there are Debian/Ubuntu patches applied to mainline kernel before compiling.
– llvs
Oct 7 at 7:14
Yes, correct, you do not get the Ubuntu kernel. My point was that incremental compiles are possible. By the way, I use mainline kernels on my 16.04 server all the time.
– Doug Smythies
Oct 7 at 15:04
It is possible to do an incremental compile, but I have never figured out how for the Ubuntu method. For the mainline kernel, I do incremental compiles all the time.
– Doug Smythies
Oct 2 at 14:28
It is possible to do an incremental compile, but I have never figured out how for the Ubuntu method. For the mainline kernel, I do incremental compiles all the time.
– Doug Smythies
Oct 2 at 14:28
Thank you. But using the Ubuntu config files on the mainline kernel does not give me the Ubuntu kernel, correct? My understanding was that there are Debian/Ubuntu patches applied to mainline kernel before compiling.
– llvs
Oct 7 at 7:14
Thank you. But using the Ubuntu config files on the mainline kernel does not give me the Ubuntu kernel, correct? My understanding was that there are Debian/Ubuntu patches applied to mainline kernel before compiling.
– llvs
Oct 7 at 7:14
Yes, correct, you do not get the Ubuntu kernel. My point was that incremental compiles are possible. By the way, I use mainline kernels on my 16.04 server all the time.
– Doug Smythies
Oct 7 at 15:04
Yes, correct, you do not get the Ubuntu kernel. My point was that incremental compiles are possible. By the way, I use mainline kernels on my 16.04 server all the time.
– Doug Smythies
Oct 7 at 15:04
add a comment
|
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1178147%2fcontinue-custom-kernel-creation-and-not-start-over-again-from-square-one%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1178147%2fcontinue-custom-kernel-creation-and-not-start-over-again-from-square-one%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It is possible to do an incremental compile, but I have never figured out how for the Ubuntu method. For the mainline kernel, I do incremental compiles all the time.
– Doug Smythies
Oct 2 at 14:28
Thank you. But using the Ubuntu config files on the mainline kernel does not give me the Ubuntu kernel, correct? My understanding was that there are Debian/Ubuntu patches applied to mainline kernel before compiling.
– llvs
Oct 7 at 7:14
Yes, correct, you do not get the Ubuntu kernel. My point was that incremental compiles are possible. By the way, I use mainline kernels on my 16.04 server all the time.
– Doug Smythies
Oct 7 at 15:04