Re: [MiNT] Magnum STe/Mintlib

[Alan Hourihane <alanh@fairlite.co.uk>]

On Thu, 2010-01-14 at 16:40 -0500, Mark Duckworth wrote:
> On 1/14/10 3:49 PM, Alan Hourihane wrote:
> > On Thu, 2010-01-14 at 15:04 -0500, Mark Duckworth wrote:
> >    
> >> On 1/14/10 2:44 PM, Mark Duckworth wrote:
> >>      
> >>> 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.
> >>>>
> >>>>          
> >>> It seems the version on your site was 20090828.  This is the mintlib
> >>> that had the issue.  The current mintlib in cvs does not.  Therefore I
> >>> think we're good to go.  But now I'm curious what the issue was.
> >>>
> >>> Thanks,
> >>> Mark
> >>>
> >>>
> >>>
> >>>        
> >> The failure occurred on open(".", O_RDONLY);  If I'm not mistaken, Alan
> >> did a lot of work on the directory open functions.  Probably can
> >> consider this a past bug that has been long since resolved.
> >>      
> > I suspect that your ext2.xfs was not updated.
> >
> > Alan.
> >
> >    
> Definitely not the case.  While I did have the ext2.xfs from a kernel of 
> a couple days ago, the kernel from that same build paniced so I upgraded 
> to a new kernel but not a new ext2.xfs.  I just updated to a new 
> ext2.xfs that matches today's kernel from your site and reinstalled 
> mintlib-20090828 and then rebuild cvs and got the error.  So it doesn't 
> seem to be related to that.  Plus the error originally came up with a 
> kernel and ext2.xfs module from early 2009.  If it's ext2.xfs then you 
> should be able to put this cvs binary on your system and it should work.
> 
> http://aoi.atari-source.org/~mduckworth/cvs.zip
> 
> Give it a shot.  The problem is fixed in current mintlib so we're just 
> discussing this for the sake of argument but it very much so appeared to 
> be in mintlib at that point in time.

I'm not going to worry about it.

Alan.