Raphael, I had to stop the build outside my chroot environment for the weekend. I will try it again today. My "normal" environment stopped cause of qt4 library issues, but that's not the same as my CMake problem.
I'm not 100% the problem is with chroot, but it could very well be. I've had other weird problems before when trying to build in chroot. For example, my path environment variable shows a path to /usr/local/sbin, yet when I try to run a program from /usr/local/sbin it won't get executed. I have to include the full path to the binary (this is a non KDE issue) ... Larry --- On Sat, 10/3/09, Raphael Kubo da Costa <[email protected]> wrote: From: Raphael Kubo da Costa <[email protected]> Subject: Re: [kde-freebsd] KDE 4 build problem in FreeBSD 7.2 with all updated ports... To: [email protected] Cc: [email protected] Date: Saturday, October 3, 2009, 4:37 PM 2009/10/3 Larry Maloney <[email protected]> > > Hello, > > I'm having essentailly the same problem as this post: > > http://forums.freebsd.org/showthread.php?t=2479&highlight=cmake > > Does anyone have any suggestions? > > Thank you, > > Larry As we've talked on IRC, it may have something to do with you building inside a chroot environment. For some reason, CMake is picking its own /usr/local/share/cmake/Modules/FindKDE4.cmake instead of kdelibs' /usr/local/kde4/share/apps/cmake/modules/FindKDE4.cmake. You said things didn't work when you built outside your chroot, but didn't say what the error was. Can you provide more details?
_______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
