On 24.09.2005 [10:19:53 -0700], Roland Dreier wrote: > Nish> I have a prototype of something similar running right now, > Nish> to help test InfiniBand, both in mainline and in the svn > Nish> repo. Basically, every night (this part hasn't been set up > Nish> yet, but should be nothing more than a crontab entry), I can > Nish> spawn a build job for InfiniBand. Currently, it will only > Nish> cover compile-testing in the following sense: build current > Nish> -git with IB options set to =y and =m in x86 and ppc64; and > Nish> build current -git with the current svn code linked and IB > Nish> options set to =y and =m in x86 and ppc64. > > This is great, thanks! The build of latest git + latest svn might not > always succeed, because we try to keep svn working with the latest > full kernel release, but it's still very helpful to get advance > warning of API changes that will break our tree. > > Nish> I have attached below my results from 2.6.14-rc2-git3. Only > Nish> build failure was the gen2 kernel code under ppc64 with > Nish> everything set to y. > > I just checked in a fix for this -- the pci_pretty_name() API has gone > away, so I removed our use of it in svn. I don't understand how your > other builds of git + svn succeeded though, since pci_pretty_name is > completely gone. Oh, I guess you'll miss link failures when building > modules, so functions that disappear won't break the build. Still, > how did the x86 =y build succeed?
And, in fact, the x86 =y build also fails, same issue (now that I've found a consistently working machine, shouldn't run into the gcc problems again; we tend not to update the test machines). Thanks, Nish _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
