Hi, I'll provide an answer to my own question. It appears that the "as" command invoked by the build script was deleting /dev/null. Cheeky monkey! I fixed it by changing the following line in darwinbuild (around line 620): echo " cctools version: \$(as -v -o /dev/null < /dev/null 2>&1 | cut -c 22- 2>/dev/null)" to: echo " cctools version: \$(as -v -o /ignore-me < /dev/null 2>&1 | cut -c 22- 2>/dev/null)" I found this problem by adding an "ls -l /dev/null" after that line and finding that /dev/null no longer existed. After this change, xnu is (so far) happily building... By the way, this was on a MacOS 10.3.9 system:
sw_vers ProductName: Mac OS X ProductVersion: 10.3.9 BuildVersion: 7W98
Cheers, dstn.
Hi,
I spent yesterday trying to get various darwin components build, using what I thought was darwinbuild 0.7.2. It turned out that I had in fact installed an older version to /usr/local/darwinbuild and modified my path to point to that one, while the new one was installed in /usr/local. Argh - that sort of thing makes me feel pretty dumb. If darwinbuild had a "-version" option I might have caught my mistake sooner - feature request?
Anyway, I've now straightened myself out but am rather quickly hitting a wall. I run "darwinbuild -init 7W98", then "darwinbuild xnu", which produces the log file attached.
I tried doing "mount -t devfs devfs BuildRoot/dev/" before running darwinbuild, with almost the same effect (it reports "devfs appears to exist").
I added a couple of lines to darwinbuild to do an "ls -l /dev/null" at the start of the build script, with this result:
Checking /dev/null: crw-rw-rw- 1 root wheel 3, 2 9 Jan 09:22 /dev/null
so it looks to me like /dev/null exists in the chrooted environment.
What's going on? Any suggestions of what I should do?
Thanks, dustin.