Thanks, Brad. I agree that programs should not have to be recompiled to call a different library function. I've added your comments to my PMR with IBM -- we'll see what they say.
>________________________________ > From: Bram Moolenaar <[email protected]> >To: John Wiersba <[email protected]> >Cc: "[email protected]" <[email protected]> >Sent: Wednesday, June 12, 2013 6:33 AM >Subject: Re: Vim 7.3 bug on AIX 6.1 with 64-bit inodes > > > >John Wiersba wrote: > >> I used -u NONE so that my configuration would be as simple as >> possible. I normally use a custom .vimrc which does not have >> compatible mode set. >> >> This buggy behavior happens only on AIX 6.1 with filesystems which >> have 64-bit inodes. It does not happen on other filesystems or other >> operating systems (Linux, SunOS). >> >> The files in my example have not been changed. It has something to do >> with vim not being able to read 64-bit inodes (such as with a >> readdir() vs readdir64() system call). >> >> When I use vim -u NONE a b, the status line says "a" 1 line, 10 >> characters. >> After :n, the status line briefly says :n (as I type it) and then >> returns to saying "a" 1 line, 10 characters. The file contents still >> are the contents of file a. After the next :n, the status line >> briefly says :n (as I type it) and then says E165: Cannot go beyond >> last file. >> >> So, vim knows I have another file in my list, but somehow cannot show >> it. And then it knows I've reached the end of the file list. Vim >> behaves normally on AIX 6.1 if my current directory (where file a and >> b are located) is on a different filesystem. >> >> >> For further information, there are other utilities that have problems >> with this same 64-bit inode filesystem, such as chmod -R, chown -R, >> make and cd from an sftp client after the sftp server process has >> cd'ed to this filesystem. These system utility bugs all have to do >> with utilities not being built with readdir64() and I have an open PMR >> with IBM to fix those. Other system utilities such as ls -R and find >> work properly. However, this is a copy of vim that I built myself. >> So somehow the normal build of vim on AIX 6.1 does not function >> properly when confronted with a 64-bit inode filesystem. When I use a >> hand-built vim 7.3 from other OSes (SunOS 5.10 or RHEL 5.5) to access >> the same filesystem, I do *not* experience this problem (vim behaves >> normally as I expect). So the problem is for AIX 6.1 only and only >> for a 64-bit filesystem. > >Vim uses readdir(). If that's not working then you should find a >library where it does work. > >I don't have a readdir64() on my system. And requiring all programs to >be rebuild with it seems the wrong way to go. Or at least giving you a >big headache. > >Note that ino_t can be 64 bit without any problems. > >-- >If you feel lonely, try schizophrenia. > >/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ >/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ >\\\ an exciting new programming language -- http://www.Zimbu.org /// >\\\ help me help AIDS victims -- http://ICCF-Holland.org /// > >-- >-- >You received this message from the "vim_dev" maillist. >Do not top-post! Type your reply below the text you are replying to. >For more information, visit http://www.vim.org/maillist.php > >--- >You received this message because you are subscribed to the Google Groups >"vim_dev" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to [email protected]. >For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
