On Thu, Aug 21, 2008 at 10:45 PM, Joseph L. Casale <JCasale at activenetwerx.com> wrote: >>There are two times when this becomes an issue. One is on x86_64 >>systems where build deps can cross architectures, and the other is >>when using systems like openvz/virtuozzo where the glibc is often >>replaced or otherwise lobotomized. >> >>Which one is yours? > > Ahh, all the CentOS boxes are either x64 Xen Dom0 or U... > What happens to glibc on these, especially in the Dom0 case where > I hand installed the xen rpm's and glibc wasn't touched after initial update? which xen rpms did you install? The ones from centos, or the ones from xensource? Generally when building for x86_64, it's best to remove all traces of x86 packages on the system. If you're doing some cross-compiling (building x86 on x86_64) then it's far easier to use a build utility like mock which creates your environment for you in a separate area. While it requires a bunch more space, it produces 'clean' rpms which are untainted by any strays packages or source installed bits you may have on the system. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell