Hi all, I have downloaded DarwinBuild with the intention to use it to build my own copy of the 10.6 kernel. I believe this will help me to be more effective at debugging my own driver and user-client code. I am experiencing a problem getting started. I downloaded and installed DarwinBuild (after first downloading and installing MacPorts). I did fine (as far as I could tell) until I got to the point of actually trying to build a kernel. DarwinBuild is installed in /opt/local/bin/. I prepared /root/xnu/ to be my build directory as shown: MacBook-Pro:xnu root# ls .build BuildRoot Headers Logs Roots Sources Symbols I moved the kernel sources that I had downloaded previously from http://www.opensource.apple.com/ to a directory under the Sources directory as shown: MacBook-Pro:xnu root# ls sources xnu-1504.9.26 When I tried to start the build, the following occurred: MacBook-Pro:xnu root# /opt/local/bin/darwinbuild xnu *** Attaching build root disk image ... /dev/disk1 GUID_partition_scheme /dev/disk1s1 EFI /dev/disk1s2 Apple_HFS /Volumes/BuildRoot_xnu_20110504142913 ERROR: project not found: xnu Would somebody please tell me what I've done wrong? Thanks. David Lee
On May 4, 2011, at 3:27 PM, David Lee wrote:
Hi all,
I have downloaded DarwinBuild with the intention to use it to build my own copy of the 10.6 kernel. I believe this will help me to be more effective at debugging my own driver and user-client code. I am experiencing a problem getting started. I downloaded and installed DarwinBuild (after first downloading and installing MacPorts). I did fine (as far as I could tell) until I got to the point of actually trying to build a kernel. DarwinBuild is installed in /opt/local/bin/. I prepared /root/xnu/ to be my build directory as shown:
What exact commands did you run and what did they output? -Bill
Bill, Unfortunately, I no longer have the output. If i remember correctly, however, I did make an error in following the procedure. After creating the build directory, I moved the kernel sources into a subdirectory of the build directory and typed: # opt/local/bin/darwinbuild xnu Without having prepped the build directory. This failed, of course. I then typed: # opt/local/bin/darwinbuild -init xnu # cd xnu # opt/local/bin/darwinbuild xnu and received the output provided before. Should I just clean up and start over without this error? I didn't think much about it at the time. It didn't seem important to me. David Lee -----Original Message----- On May 4, 2011, at 3:27 PM, David Lee wrote:
Hi all,
I have downloaded DarwinBuild with the intention to use it to build my own copy of the 10.6 kernel. I believe this will help me to be more effective at debugging my own driver and user-client code. I am experiencing a problem getting started. I downloaded and installed DarwinBuild (after first downloading and installing MacPorts). I did fine (as far as I could tell) until I got to the point of actually trying to build a kernel. DarwinBuild is installed in /opt/local/bin/. I prepared /root/xnu/ to be my build directory as shown:
What exact commands did you run and what did they output? -Bill
On May 5, 2011, at 9:40 AM, David Lee wrote:
Bill,
Unfortunately, I no longer have the output. If i remember correctly, however, I did make an error in following the procedure. After creating the build directory, I moved the kernel sources into a subdirectory of the build directory and typed:
# opt/local/bin/darwinbuild xnu
Without having prepped the build directory. This failed, of course. I then typed:
# opt/local/bin/darwinbuild -init xnu
-init takes a path to a build plist, or a build number in which case it'll get the plist from the svn repo. You probably want "... -init 10J869" here instead. See the plists directory in the repo for other build choices. http://svn.macosforge.org/repository/darwinbuild/trunk/plists/ -Bill
Bill, I'm not sure if I'm in good shape yet or not. Could you please have a look at the attached file. My build did quite a lot of stuff and took quite a bit of time, but I'm not sure if it was fully successful. It did produce what appeared to me to be some error messages. Also I'm not finding a file produced named "mach_kernel", but it's been my experience that files with this name are difficult to see with Finder. Apparently it likes to hide them. (By the way, if you could tell me how to find files named "mach_kernel" I would appreciate it much.) Thanks in advance. David lee -----Original Message----- On May 5, 2011, at 9:40 AM, David Lee wrote:
Bill,
Unfortunately, I no longer have the output. If i remember correctly, however, I did make an error in following the procedure. After creating the build directory, I moved the kernel sources into a subdirectory of the build directory and typed:
# opt/local/bin/darwinbuild xnu
Without having prepped the build directory. This failed, of course. I then typed:
# opt/local/bin/darwinbuild -init xnu
-init takes a path to a build plist, or a build number in which case it'll get the plist from the svn repo. You probably want "... -init 10J869" here instead. See the plists directory in the repo for other build choices. http://svn.macosforge.org/repository/darwinbuild/trunk/plists/ -Bill
The exit status of 2, along with the error messages, means it did not complete successfully. What version of Xcode are you using? Darwinbuild does not do well with Xcode 4 currently. -Bill On May 5, 2011, at 4:17 PM, David Lee wrote:
Bill,
I'm not sure if I'm in good shape yet or not. Could you please have a look at the attached file. My build did quite a lot of stuff and took quite a bit of time, but I'm not sure if it was fully successful. It did produce what appeared to me to be some error messages. Also I'm not finding a file produced named "mach_kernel", but it's been my experience that files with this name are difficult to see with Finder. Apparently it likes to hide them. (By the way, if you could tell me how to find files named "mach_kernel" I would appreciate it much.) Thanks in advance.
David lee
-----Original Message-----
On May 5, 2011, at 9:40 AM, David Lee wrote:
Bill,
Unfortunately, I no longer have the output. If i remember correctly, however, I did make an error in following the procedure. After creating the build directory, I moved the kernel sources into a subdirectory of the build directory and typed:
# opt/local/bin/darwinbuild xnu
Without having prepped the build directory. This failed, of course. I then typed:
# opt/local/bin/darwinbuild -init xnu
-init takes a path to a build plist, or a build number in which case it'll get the plist from the svn repo. You probably want "... -init 10J869" here instead. See the plists directory in the repo for other build choices.
http://svn.macosforge.org/repository/darwinbuild/trunk/plists/
-Bill
<kernelbuildlog.zip>
Bill, Xcode version 3.2.6. David Lee -----Original Message----- The exit status of 2, along with the error messages, means it did not complete successfully. What version of Xcode are you using? Darwinbuild does not do well with Xcode 4 currently. -Bill On May 5, 2011, at 4:17 PM, David Lee wrote:
Bill,
I'm not sure if I'm in good shape yet or not. Could you please have a look at the attached file. My build did quite a lot of stuff and took quite a bit of time, but I'm not sure if it was fully successful. It did produce what appeared to me to be some error messages. Also I'm not finding a file produced named "mach_kernel", but it's been my experience that files with this name are difficult to see with Finder. Apparently it likes to hide them. (By the way, if you could tell me how to find files named "mach_kernel" I would appreciate it much.) Thanks in advance.
David lee
-----Original Message-----
On May 5, 2011, at 9:40 AM, David Lee wrote:
Bill,
Unfortunately, I no longer have the output. If i remember correctly, however, I did make an error in following the procedure. After creating the build directory, I moved the kernel sources into a subdirectory of the build directory and typed:
# opt/local/bin/darwinbuild xnu
Without having prepped the build directory. This failed, of course. I then typed:
# opt/local/bin/darwinbuild -init xnu
-init takes a path to a build plist, or a build number in which case it'll get the plist from the svn repo. You probably want "... -init 10J869" here instead. See the plists directory in the repo for other build choices.
http://svn.macosforge.org/repository/darwinbuild/trunk/plists/
-Bill
<kernelbuildlog.zip>
Bill, I'm still interested in getting this working. David Lee Bill, Xcode version 3.2.6. David Lee -----Original Message----- The exit status of 2, along with the error messages, means it did not complete successfully. What version of Xcode are you using? Darwinbuild does not do well with Xcode 4 currently. -Bill On May 5, 2011, at 4:17 PM, David Lee wrote:
Bill,
I'm not sure if I'm in good shape yet or not. Could you please have a look at the attached file. My build did quite a lot of stuff and took quite a bit of time, but I'm not sure if it was fully successful. It did produce what appeared to me to be some error messages. Also I'm not finding a file produced named "mach_kernel", but it's been my experience that files with this name are difficult to see with Finder. Apparently it likes to hide them. (By the way, if you could tell me how to find files named "mach_kernel" I would appreciate it much.) Thanks in advance.
David lee
-----Original Message-----
On May 5, 2011, at 9:40 AM, David Lee wrote:
Bill,
Unfortunately, I no longer have the output. If i remember correctly, however, I did make an error in following the procedure. After creating the build directory, I moved the kernel sources into a subdirectory of the build directory and typed:
# opt/local/bin/darwinbuild xnu
Without having prepped the build directory. This failed, of course. I then typed:
# opt/local/bin/darwinbuild -init xnu
-init takes a path to a build plist, or a build number in which case it'll get the plist from the svn repo. You probably want "... -init 10J869" here instead. See the plists directory in the repo for other build choices.
http://svn.macosforge.org/repository/darwinbuild/trunk/plists/
-Bill
<kernelbuildlog.zip>
participants (2)
-
David Lee
-
William Siegrist