Success! Got gtk2 + xorg-modular built in SYSROOT-environment

Mike A. Harris mharris at
Wed Oct 5 23:30:29 PDT 2005

Daniel Stone wrote:

>>Sounds like installing an OS into a subdirectory, tweaking various
>>config files, device files, mountpoints, etc. within that subdir's
>>OS installation, and then chrooting into that dir to build.
>>Is that how sysroot works?  If it is similar that, autotools
>>works fine in such environments (as did Imake).
>>The Red Hat buildsystem (beehive) as well as other buildsystems
>>such as mock, mach, etc. use an approach similar to this.
>>I'm not too sure how this relates to X.Org architecture though.
> As far as I can tell, it's almost exactly as you've described, but
> without the chroot step, so everything on the planet needs to be
> patched to prepend $SYSROOT to some indeterminate paths, but not
> others.

Sounds broken to me.  It would seem to be easier to use an existing
buildsystem mechanism with chroot that works and works well, than
to patch the build process of hundreds or thousands of software
packages to work with some new system no?

Maybe I'm overlooking some net gain of the experimental system
being proposed that isn't jumping out at me. ;o)

(Removed gtk-devel off the CC, as that's annoying.)

More information about the xorg-modular mailing list