From mint-bounce@lists.fishpool.fi Thu Jan 14 14:29:46 2010 Message-ID: <4B4F6FAB.40002@atari-source.org> Date: Thu, 14 Jan 2010 14:25:31 -0500 From: Mark Duckworth User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: Alan Hourihane CC: mint@lists.fishpool.fi Subject: Re: [MiNT] Magnum STe/Mintlib References: <4da966f01001131059h616973c3uda0adf12102ccbd9@mail.gmail.com> <4B4E1D55.2020607@atari-source.org> <4B4F4637.5030705@atari-source.org> <1263493074.16683.4297.camel@jetpack.demon.co.uk> <4B4F63A9.7080206@atari-source.org> <1263497083.16683.4299.camel@jetpack.demon.co.uk> In-Reply-To: <1263497083.16683.4299.camel@jetpack.demon.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mduckworth@atari-source.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On 1/14/10 2:24 PM, Alan Hourihane wrote: > 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. > > 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.... Thanks, Mark