Mmm... yep, that launchd patch is what's missing. I added it to git: http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=commit;h=e8d4cefa0837... Would you mind checking your other patches and making sure they're all in git or www.opensource.apple.com. If not, would you mind tarballing them and putting them somewhere for me, and I'll work on massaging them into git? --Jeremy On Dec 10, 2007, at 22:12, Ben Byer wrote:
On Dec 10, 2007, at 9:17 PM, Jeremy Huddleston wrote:
On Dec 10, 2007, at 21:07, Ben Byer wrote:
Nothing jumps out at me as obvious -- I assume you've checked using otool -L to make sure that xterm is really linking against the correct libX11 (and not one from MacPorts, or something -- although we should fix that in MacPorts, too :))
Can you put up the binary you're generating for libX11 somewhere? I'll disassemble it and compare it to what I get when I build with those flags.
http://people.freedesktop.org/~jeremyhu/libX11.6.2.0.dylib-broken.bz2
Argh, okay, I think I see the problem. Internally, I maintain tarballs for each package, and occasionally a set of patches to be applied against that tarball. What gets put up on www.opensource.apple.com is taken from the build process after the patches are applied. Try adding these three patches (you may only actually need one of them)
<defines.diff><dummyfiles.diff><launchd.patch>
-- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer