Re: Kernel build problem
Re: Kernel build problem
- Subject: Re: Kernel build problem
- From: Felix Kronlage <email@hidden>
- Date: Fri, 28 May 2004 21:29:06 +0200
- Organisation: OpenDarwin.org - http://www.opendarwin.org/
On Fri, May 28, 2004 at 09:18:04AM -0500, Steven Bytnar wrote:
>
You should try applying parts of this diff that make sense:
>
http://www.opendarwin.org/~fkr/xnu/make-xnu-517.3.7-compile.diff
>
In particular, check out this part:
>
diff -urN xnu-517.3.7/osfmk/ppc/chud/chud_spr.h xnu-517.3.7-patched/osfmk/ppc/chud/chud_spr.h
>
--- xnu-517.3.7/osfmk/ppc/chud/chud_spr.h Fri Dec 19 23:38:23 2003
>
+++ xnu-517.3.7-patched/osfmk/ppc/chud/chud_spr.h Tue Dec 30 22:01:26 2003
>
>
Things like this have been a recurring problem for many of the XNU releases
>
for 10.3.x. It's very annoying. It makes it a pain in the butt to rebuild
>
anything from the Apple provided source snapshots without applying some
>
amount of patches.
>
>
Instead of building the Apple source snapshots directly, you will have better
>
luck with the opendarwin CVS version (which is currently the 10.3.2 kernel
>
though *cough* *cough*):
>
http://cvs.opendarwin.org/index.cgi/src/xnu/
>
where this problem is fixed:
>
http://cvs.opendarwin.org/index.cgi/src/xnu/osfmk/ppc/chud/chud_spr.h
yes, I have not done any more imports since I still want to finish a
release with what we got. Also importing (and doing all the merging
including removing cruft) takes _a_lot_ of time, especially considering
there are not a lot of active helpers out there. Likely I'll will not
import the full source of Darwin in the future, mainly to not waste
valuable time that much rather is spent hacking on useful stuff
(like wireless support, xnu, etc. etc.) and making somewhat useful
releases from the tarballs that Apple releases (plus the stuff we
develope).
Likely (especially because people asked me) I'll keep importing xnu and
of course other third party sources that we work on, things like ncutil,
yum, rpm.
With the tarballs from Apple and the DarwinPorts Portfiles in src/Ports
we can easily build the sources and with adding Patchfiles even patch
things without the hassle of importing/merging, so this will hopefully
allow me to concentrate more on the real nifty things ;)
I agree with people that it's much nicer to see code changes in cvs, but
too few people (at least it seems like that) make use of our cvs to actually
see such changes that it is not worth the effort.
>
If you want the 10.3.4 kernel, you'll need to fix the source yourself.
>
If you want a wrapped up kernel that's likely to build without problems,
>
use the one in opendarwin CVS.
I'll take a look tonight and see about providing a tarball.
-fkr
--
gpg-fingerprint: 076E 1E87 3E05 1C7F B1A0 8A48 0D31 9BD3 D9AC 74D0
Felix Kronlage | FKR-RIPE |
http://www.hazardous.org/fkr/
fkr@{grummel.net|opendarwin.org} |
http://www.opendarwin.org/~fkr/
_______________________________________________
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.