On Tue, 2006-02-21 at 14:56 -0500, Jim Paris wrote: > Michel Dänzer wrote: > > On Fri, 2006-02-17 at 18:00 -0500, Paul Donohue wrote: > > > I suspect some of the problems are due to the autoconfage only having > > been added relatively recently; it might be better to contain cvs -D to > > the src directory and use the current code for the rest. > > The autoconf stuff was added after 6.9.0, wasn't it?
Yes and no. :) 6.9 (monolithic) and 7.0 (modular) were released at the same time, the latter was only created as a repository-side copy shortly before the releases, the autoconfage was added before that. > > As a little consolation, let me point out that this kind of thing > > would usually require at least a bunch of rebuilds of the whole > > monolithic X tree before the modularization > > I don't see how that can be avoided in this case, as the tree was > still monolithic when these bugs were introduced. That's true, but it doesn't necessarily prevent older driver code from building (with the autoconf build system) and running against the current server. I suspect the fact that the current server uses dlloader as opposed to elfloader modules is actually more likely to cause trouble than autoconf, the more so the further back you go. Then again, I just remembered a specific problem with autoconf: older driver code didn't include config.h. Adding -include config.h to CFLAGS might help with that. Or maybe there's really no way around the monolithic tree for this. :} -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
