On 1/14/10 2:24 PM, Alan Hourihane wrote:
I am and I did. I compiled the absolute latest mintlib from cvs with gcc 2.95.3 and 4.4.2 and I'm not experiencing the problem now. I'm confused. I was using the mintlib version that was on your site and that's the version that exhibited the problem I believe. But maybe you didn't even build that with 4.4.2....On Thu, 2010-01-14 at 13:34 -0500, Mark Duckworth wrote:On 1/14/10 1:17 PM, Alan Hourihane wrote:On Thu, 2010-01-14 at 11:28 -0500, Mark Duckworth wrote:Hello all, I ordered the Magnum STe PCB prototype to be produced last night :) Also, I discovered a problem with mintlib. If you install mintlib cvs (get a build from Alan's site), then rebuild the cvs rpm (rpm --rebuild cvs-xxxx.src.rpm), then install the newly built rpm. If you check out the freemint cvs, all is well, but if you move into the freemint cvs directory and do cvs up to update, it gives the error root@arawork:/root/temp/freemint>cvs up cvs update: cannot open current directory: Is a directory I have tried new versus old kernel, gcc 2.95.3 vs 4.4.2, and other things. I have isolated this to be something in the mintlib causing it.What kernel are you running ? Alan.I tried with both an early 2009 kernel and trunk off your site built at midnight today. I'm still experimenting to ensure that mintlib is the problem.Are you running of an ext2 drive ? If so, did you update the ext2 XFS from the tarball too ? Alan.
Thanks, Mark