Darrell, Slavek, Can you confirm the size of the python-trinity package you are building. I built python-trinity last night for the first time and I was bewildered by the fact it took 20 minutes to build and resulted in a package that was over 20M. 10:51 phoinix:/dat_e/tde/pkg> l i686/tde-python-trinity-R14preRC1-1-i686.pkg.tar.xz -rw-r--r-- 2442140 Feb 10 04:01 i686/tde-python-trinity-R14preRC1-1-i686.pkg.tar.xz During the build, there was a wholesale lack of any build output. At times I thought the build was hung, but checking with top, the build was cranking away with cclplus pegging one of the cores at 100%. I don't know if a library path change is needed or whether the build just spins it wheels looking through /lib, but something seems like it is caught in a race condition. There is also a hardcoded search path for KDE353 or kde353 stuck in the build somewhere. What are others seeing? -- David C. Rankin, J.D.,P.E.