[haiku-development] Re: replacing kernel (was Re: replacing runtime_loader)
- From: Dániel Kasza <daniel@xxxxxxxx>
- To: Axel Dörfler <haiku-development@xxxxxxxxxxxxx>
- Date: Tue, 3 May 2016 21:24:01 -0400
On Fri, Mar 25, 2016 at 1:57 PM, waddlesplash <waddlesplash@xxxxxxxxx>
wrote:
On Fri, Mar 25, 2016 at 1:55 PM, Tim Kelly <gtkelly@xxxxxxxxxxxxxxxxx>
wrote:
Thank you for the clarification. As I understand it, this requires
building
a full disk image and installing from it, correct? That there is no
target
for jam that will install the new kernel and related files over (or
parallel
to) the existing installation?
No, you can "jam haiku.hpkg" and then "pkgman install
path/to/built/haiku.hpkg".
-waddlesplash
Is there any other way?
I am working on adding mlock() and munlock() calls, and having to build
haiku.hpkg every time is a huge waste of time and the package does not work
reliably either:
- I can install the package, but if I build another package and try to
install that, a window pops up and tells me that I have to uninstall
everything else...
- ...after pkgman told me that my package is installed!
- I cannot build software after I install my own build. C headers are
missing.
So far, the only way I can make a working build is to `jam @release-cd` and
install from the CD. This takes even longer than building haiku.hpkg.
I am sure this is not an issue for kernel developers as they know how to
work around this and/or they write code that works without testing, but it
is a problem for me. I am not familiar with the codebase and if it takes me
an hour to test a 2 line change, Haiku might never have an mlock()
impelementation. Please help! :)
Thanks,
Daniel
Other related posts:
