[Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

OrigBitmancer · 2019-09-25 04:51:24

In https://wiki.archlinux.org/index.php/Ke … m#Updating
near the end, there is the text:

Then run manually most, if not all, of PKGBUILD::prepare().

Does the author expect the average wiki reader to be able to perform that operation?

I can find PKGBUILD::prepare(), as a function, but I do not know how to use bash to invoke just the function part of the script.

All I can think of, is to use brute force to drive the solution. I would be grateful for illumination on any other method.
One would trace the shell through PKGBUILD down to prepare(), use the variable values we have traced, comment out
all the source outside prepare() and run the remaining shell?

I may have taken an extra dose of stupid tonight, but I cannot see any other way?

Last edited by OrigBitmancer (2019-09-28 15:32:10)

loqs · 2019-09-25 11:56:10

If you change the source entry in the PKGBUILD instead of using git commands on the checked out source tree then you can use one of the following:

makepkg -C (will clean the src dir first so everything will be rebuilt)
rm src/linux/.scmversion then the prepare function should be able to be run again by makepkg

Lone_Wolf · 2019-09-25 12:57:36

Maybe combining some makepkg options would work ?
nobuild and noextract come to mind.

man makepkg for details.

OrigBitmancer · 2019-09-28 15:24:10

loqs wrote:

If you change the source entry in the PKGBUILD instead of using git commands on the checked out source tree then you can use one of the following:
makepkg -C (will clean the src dir first so everything will be rebuilt)

Rats. I had hoped to avoid complete recompile.

loqs wrote:

rm src/linux/.scmversion then the prepare function should be able to be run again by makepkg

A VERY LATE thank you to @loqs again.

Last edited by OrigBitmancer (2019-09-28 15:28:16)

OrigBitmancer · 2019-09-28 15:28:57

A VERY LATE thank you to @Lone_Wolf

ewaller · 2019-09-28 16:17:42

OrigBitmancer,

Please try not to use [CLOSED] as that denotes a thread that has been closed by the moderation staff. Please use [SOLVED] or [RESOLVED] instead.
Thanks

OrigBitmancer · 2019-10-01 08:32:38

If it was abandoned, what code word to use?

Lone_Wolf · 2019-10-01 11:21:27

If you feel the question is answered, but don't want to continue building , resolved still applies.

In case you feel the question is NOT answered but don't want to solve it anymore,
THEN you can use abandoned.

Arch Linux

#1 2019-09-25 04:51:24

[Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

#2 2019-09-25 11:56:10

Re: [Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

#3 2019-09-25 12:57:36

Re: [Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

#4 2019-09-28 15:24:10

Re: [Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

#5 2019-09-28 15:28:57

Re: [Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

#6 2019-09-28 16:17:42

Re: [Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

#7 2019-10-01 08:32:38

Re: [Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

#8 2019-10-01 11:21:27

Re: [Closed] Kernel custom Q from Wiki:: Kernel/Arch_Build_System page

Board footer