As you've noticed, DarwinBuild appears to be missing the Kerberos's dependency information. Kerberos is a bit of a pathological case, since it requires Xcode to build, and it requires API that is not available on a pure-Darwin system. Luckily I think the dependency and API issues can be worked around by passing -nochroot to the darwinbuild command. This instructs DarwinBuild to build "out in the open" and gives it access to things that Kerberos will need, like the CoreServices framework. However, it appears the Kerberos relies on some PrivateHeaders from the Security framework, so to take this approach you'd need to install them on your base system. They're available at <http:// darwinsource.opendarwin.org/Headers/8C46/Security.hdrs.tar.gz>. There's a second issue, which is that DarwinBuild tries to produce universal binaries by default. You'll need to update to the latest DarwinBuild in CVS to get a bug fix related to editing build information. I also had to make a change to the default 8B15.plist, so you'll need to reload that. After upgrading darwinbuild, from your build directory: # rm .build/8B15.plist # darwinbuild -init 8C46 # darwinxref -b 8A428 edit Change the RC_ARCHS="ppc i386"; line in the environment dictionary to: RC_ARCHS="ppc"; Then you should be able to build Kerberos! Thanks, - Kevin On Jul 28, 2005, at 12:05 PM, John Cebasek wrote:
Hi All:
So I got a little further by building the kernel (xnu) first. That caused quite a few dependent projects to be loaded and built. So that fixes the missing make, date, localhost problem.
But now when I try and build Kerberos, I get a few errors that I can't figure out. The first is:
"C compiler cannot create executables" and the second is: cd /private/var/tmp/Kerberos/Kerberos-62.sym/BuiltProducts/ Kerberos5.intermedia tes/build/util/et: No such file or directory.
To (try) and correct the first error, I did an archive and install of Tiger and then reinstalled xCode 2.1 just incase there was a problem when I did the update from xCode 2.0 to 2.1.
But it didn't seem to do much.
Any suggestions on to how to correct these errors?
Thanks in advance for your time.
Best Regards
John Cebasek johnc@cryptocard.com