From: Hazen B. <hba...@ma...> - 2007-12-03 01:18:07
|
On Nov 28, 2007, at 12:34 AM, Alan W. Irwin wrote: > On 2007-11-27 22:49-0500 Hazen Babcock wrote: > >> >> Alan, >> >> Any ideas about this one? It looks like several changes were made to >> get-drv-info and drivers/CMakeLists.txt between 5.8.0-RC1 and >> 5.8.0. Do you >> think that one of them could have led to the problems that Marius >> is having? > > There is a real art to debugging build problems remotely, but you > are lucky > here that you have a similar platform to Marius. I suggest you try > to mimic > Marius's exact build method (cmake options including an in-source > build if > that is what he did) and tool chain (e.g., cmake version) as much as > possible. Get him to tell you his exact cmake options and give you the > cmake.out and make.out from a clean build, and compare it with > yours. Try > his exact cmake options yourself. Make sure you have the same > version of the > libltdl library that he does, etc. Get Marius to execute get-drv-info > in several different experimental ways, and you do the same. We did have a different version of libtool but I switched to the same version and I still do not see this problem. It looks to me like get- drv-info is confused on Marius's platform and is looking for the drivers in the install directory rather than in the build directory. The source of the confusion seems to be plGetDrvDir() returning the wrong directory, likely because (1) it is in turn misled by plInBuildTree() or (2) the BUILD_DIR environment variable is set incorrectly. This would be easier to sort out if there was a flag for debugging output from pldebug() during the build. Is there such a thing? -Hazen |