On Mon, Mar 16, 2009 at 12:09 PM, Barton C Massey <b...@cs.pdx.edu> wrote: > In message <20090316055209.ga4...@comet> you wrote: >> On 07:48 Sun 15 Mar , David Wuertele wrote: >> > I tried compiling libX11-1.2 but it asked for >> > libxcb-1.1.92 or newer. I tried compiling libxcb-1.1.92 >> > but it asked for python-2.5 or newer. Because of the >> > crazy package dependencies in my workstation, upgrading >> > its python-2.3 to python-2.5 is impossible (hooray for >> > outsourced IT). Also, my build script has to work for >> > dozens of developers who have the same python version as >> > me and the same inability to upgrade. I forced libxcb's >> > configure script to accept my python version, but then >> > libxcb died during the build due to the incompatibility. >> > >> > Stymied by the python requirement, I tried backing down >> > to libxcb-1.1 which doesn't require it. That compiled >> > fine. But now I had to back down to libX11-1.1. >> > libX11-1.1's build failed due to what appears to be a >> > known > bug. Googling says that the only cure is to go >> > to libX11-1.2! >> >> This should do the trick with libX11: >> >> ./configure --without-xcb > > Also, the Python is only used to generate some generic C > code. So if you want to stick with Xlib/XCB, just build > xcb/proto and xcb/libxcb on some machine with newer Python > and copy the generated C files over.
Is the C platform-independent? Maybe we could add get it in dist? Just drop all the nodist_ from src/Makefile.am. I think that would be really nice to not require python while bootstrapping X. -- Dan _______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg