On 03/19/2012 02:22 PM, Darrell Anderson wrote:
> No, I don't. I have $PKG_CONFIG_PATH=/opt/trinity/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/lib/pkgconfig and LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity in my build environment. Perhaps that is the difference?

Darrell,

   The problem was that the cmake files made no inclusion of the library 
search path -L/opt/trinity/lib. In the case of kpowersave, the library not 
found was libdbus-tqt-1 which apparently was the first lib in /opt/trinity/lib 
that was needed at the 96% point in the build (see original post)

   Since I made no adjustment to any of the search paths, the build would 
fail. You system works great, probably because you explicitly include the 
various search paths in your CXXFLAGS (or similar) flags you  provide. What 
I'm doing is taking the bare environment I have and, without any modifying 
flags, attempting the builds. That is apparently what is catching the holes in 
the build files. I think that after we catch these holes that can bite people 
during the build, we will have a much more robust set of cmake files that will 
work regardless of prefix used (/opt, /usr, ...)



-- 
David C. Rankin, J.D.,P.E.