Your defeating the purpose of ccache by putting the cache directory in a tmpfs mount. /ram is unmounted on each reboot, essentially deleting the cache directory. No wonder it isn't working. The cache directory for ccache needs to be on disk so it's persistent.
Do the following, assuming your...
Then you don't have things configured correctly. synth works well with ccache.
What is the output of cat /usr/local/etc/synth/synth.ini on the machine?
I'm guessing from reading your posts above you possibly have your system set to delete files and folders in the /tmp directory when rebooting. That would of course delete the cache as well. Set your cache directory to another directory so it doesn't get deleted on reboot if this is the case or...
zipitup, for future reference you can mark a thread you created yourself solved by clicking on "Edit Thread" in the upper right while viewing the thread.
You'll want to delete all files and folders in /usr/ports. If you want, you can copy the /usr/ports/distfiles directory somewhere else temporarily as not to have to download all the distfiles again once /usr/ports is repopulated, but it won't cause any harm otherwise to delete that directory as...
Sure, it can work. I have a a single disk system here at home in fact using the same method to dual boot though it did fail to boot once during a FreeBSD upgrade from 9.3-RELEASE to 10.0-RELEASE and I rarely turn it on anymore as it's quite an old system. If you know what your doing it's...
For anyone that doesn't keep up with the mailing lists and is interested or curious about the status of the work being done to package the base system with pkg , Glen Barber has posted some information about it on the new freebsd-pkgbase mailing list...
Just thought I'd add that while I prefer to stick to CLI based tools to work with CD/DVDs and use security/sudo myself when needed, there are a few ports(sysutils/k3b-kde4 is one IIRC) that require you to use the method asteriskRoss mentioned he preferred in his above post #9 in order to work...
My suspicion is that the driver(s) won't be backported, at least not in time for 10.3-RELEASE, which is due to release in March. If you can wait a few more months longer and or work around it, 11.0-RELEASE should also be available and supported, which will have the driver available.
Ok. I haven't tried on 10.2-STABLE or 10.2-RELEASE yet so I'll take your word it builds fine. Since this is an issue with CURRENT, not sure where to go from here other than the mailing lists.
...Not sure why the site is being blocked however we try to discourage people from posting long logs directly to posts here as not to clutter up threads. I'll send you a PM with the log contents to read since your accessing the forums fine.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.