README refers to binaries which do not exist (`bin/darwinbuildheaders` etc.)

[barracuda156]

Is it outdated or am I missing something? There are no darwinbuildheaders and installheaders, and there seems to be no straightforward way to install private headers for everything at once, which README refers to.

[barracuda156]

Is there a way to install headers produced by darwinbuild -headers into buildroot? installheaders does not exist.

[bhuntsman]

darwinbuild -headers -load

If you look at the source code you can see from the help text what options are available.

[barracuda156]

I will try that, thank you.

As of now, about a 100 projects built (ppc+i386+x86_64), though mostly standard Unix stuff; xnu does not want to even install headers (with those weird errors I mentioned earlier, and in a few cases builds appear to have genuine bugs (“compiler cannot build executables” is clearly a false claim, for example, since it is on standard 10.6.8 with Rosetta).

[bhuntsman]

It's going to be pretty hard, lots of things can't be built without a starter environment built at Apple... also remember that some of the sources had to have patches applied to deal with things that Apple didn't open source.

[barracuda156]

I added some patches when I written a port for libdispatch, but was thinking Darwinbuild handles its patching. Doesn’t it not?

I wanna see how it goes unmessed, but then will need to patch select sources to fix some 10.6 bugs (expose pthred_threadid and try tracking down a bug breaking UDP in 10.6).

P. S. Just in case, do you have an idea of UDP in macOS? In our case of 10.6.8 it seems that userland does not sees replies that the kernel gets, and with no UDP both DNS and DHCP are broken.