Re: XNU Kernel compiling problem
Re: XNU Kernel compiling problem
- Subject: Re: XNU Kernel compiling problem
- From: Jim Magee <email@hidden>
- Date: Thu, 4 Apr 2002 15:32:13 -0800
On Thursday, April 4, 2002, at 01:48 PM, Daniel Hazelbaker wrote:
I am trying to compile the xnu kernel package for Darwin and am
getting errors. I keep getting an "-fapple-kext invalid option" from
the cc1plus program which stops the compile. I have searched on the
web and can find nothing about this option but do not want to just
remove it from the Makefile as it sounds like it is related to the
kextd program and would be required to make a valid mach_kernel.
As my teachers in grade school always used to say: "Do not move on to
the next topic." You are trying to compile a kernel version which
expects a certain version of the compiler be installed, without having
that compiler. Believe me, this will be the least of your worries. We
make newer versions of the kernel and things available in CVS because we
want you to be able to see what's going on. You will not always be able
to build and/or run that code on any existing binary systems that are
currently installable.
Stick with the versions of projects that match the released versions of
Darwin/Mac OS X if you want to be able to build and/or use them reliably.
Perhaps you will know of another way to accomplish what I am
trying to do, but my purpose for recompiling the kernel, right now, is
to disable the sleep feature when my ibook lid is put down. I want to
modify the kernel so instead of going to sleep it simply turns off the
display to prevent overheating the screen and continues to run. I know
the loginwindow.app application is what gives the kernel the sleep
options because my computer will not go to sleep before that
application loads, but I cannot find any API calls to re send that
information and disable it again.
The machine may not cool effectively enough when the lid is closed,
regardless of the screen being dim. In that case, the platform drivers
probably won't let you do what you are trying to do. It is they, the
platform and device drivers, not the kernel nor loginwindow.app, that
make the call. The kernel simply provides a means to reflect the
current power states to the different components that are interested.
The actions to be taken in response to those state transitions is up to
the drivers. From this perspectve, the kernel is also a driver, and
sleeps/wakes up the CPU(s) in response to these requests.
The reason things are different after loginwindow than before, is that
many EngerySaver preferences are maintained per-user. Until someone
logs in, we don't know what those preference values are.
--Jim
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.