Hey Ben, I asked you this before but never really responded to your response. I'm having trouble compiling a working libX11 on my own. Your compiled 1.1.3 version works fine, but when I drop in the one I compile, I get breakage: (17:23:05 Mon Dec 10 2007 jeremy@tifa i386) ~/src/freedesktop/src $ xterm _X11TransSocketINETConnect() can't get address for /tmp/launch- R9Xor0/:6000: nodename nor servname provided, or not known xterm Xt error: Can't open display: /tmp/launch-R9Xor0/:0 --- I compiled it using: --disable-xf86bigfont --without-xcb --disable-static CFLAGS="-Wall -O2 -arch i386 -arch ppc -arch x86_64 -arch ppc64 -pipe - DNO_ALLOCA -D__DARWIN__ -DHAVE_LAUNCHD" I also have the latest git of xtrans (which is where _X11TransSocketINETConnect() comes from). What am I missing here? --Jeremy
On Dec 10, 2007, at 6:29 PM, Jeremy Huddleston wrote:
I asked you this before but never really responded to your response. I'm having trouble compiling a working libX11 on my own. Your compiled 1.1.3 version works fine, but when I drop in the one I compile, I get breakage:
(17:23:05 Mon Dec 10 2007 jeremy@tifa i386) ~/src/freedesktop/src $ xterm _X11TransSocketINETConnect() can't get address for /tmp/launch- R9Xor0/:6000: nodename nor servname provided, or not known xterm Xt error: Can't open display: /tmp/launch-R9Xor0/:0
I compiled it using: --disable-xf86bigfont --without-xcb --disable-static CFLAGS="-Wall -O2 -arch i386 -arch ppc -arch x86_64 -arch ppc64 - pipe -DNO_ALLOCA -D__DARWIN__ -DHAVE_LAUNCHD"
I also have the latest git of xtrans (which is where _X11TransSocketINETConnect() comes from). What am I missing here?
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. -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer
Yeah, I completely sanitize my environment of MacPorts. Also, if it was using the macports libX11, dropping your compiled one into /usr/ X11/lib wouldn't fix the problem... Can you please look into this? I've been beeting my brain. Is there something you have not commit to libxtrans maybe that I'm missing? Can you test this out: export CFLAGS="-Wall -O2 -arch i386 -arch ppc -arch x86_64 -arch ppc64 -pipe -DNO_ALLOCA -D__DARWIN__ -DHAVE_LAUNCHD" tar xjf libX11-1.1.3.tar.bz2 cd libX11-1.1.3 ./configure --prefix=/usr/X11 --mandir=/usr/X11/man --disable- dependency-tracking --disable-xf86bigfont --without-xcb --disable-static make sudo cp /usr/X11/lib/libX11.6.2.0.dylib /usr/X11/lib/ libX11.6.2.0.dylib.working sudo make install xterm On Dec 10, 2007, at 21:07, Ben Byer wrote:
On Dec 10, 2007, at 6:29 PM, Jeremy Huddleston wrote:
I asked you this before but never really responded to your response. I'm having trouble compiling a working libX11 on my own. Your compiled 1.1.3 version works fine, but when I drop in the one I compile, I get breakage:
(17:23:05 Mon Dec 10 2007 jeremy@tifa i386) ~/src/freedesktop/src $ xterm _X11TransSocketINETConnect() can't get address for /tmp/launch- R9Xor0/:6000: nodename nor servname provided, or not known xterm Xt error: Can't open display: /tmp/launch-R9Xor0/:0
I compiled it using: --disable-xf86bigfont --without-xcb --disable-static CFLAGS="-Wall -O2 -arch i386 -arch ppc -arch x86_64 -arch ppc64 - pipe -DNO_ALLOCA -D__DARWIN__ -DHAVE_LAUNCHD"
I also have the latest git of xtrans (which is where _X11TransSocketINETConnect() comes from). What am I missing here?
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. -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer
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
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) -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer
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
They're all in www.opensource.apple.com -- applied to each respective problem. In theory, you could get them by downloading all of that code and running diff, but that's silly. I *think* this should be all of them. X11proto didn't have any patches, and X11server doesn't really apply. On Dec 10, 2007, at 11:03 PM, Jeremy Huddleston wrote:
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
Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer
participants (2)
-
Ben Byer
-
Jeremy Huddleston