On 2011-03-23, Tony Mechelynck wrote:
> On 23/03/11 08:43, Gary Johnson wrote:
> >I built Vim 7.3.0 on my Cygwin system last August and thought it
> >could use an update, so I pulled and updated the latest changes from
> >the Mercurial repository, ran "make distclean" and
> >
> > ./configure --prefix=/usr/local --with-features=huge --without-x
> > --enable-gui=no
> >
> >(one line) as I always do for Cygwin and got a bunch of error
> >messages before configure exited. I tried again with "make
> >distclean" and a simpler configure command that also tried to fix a
> >curses library problem reported by the previous run:
> >
> > ./configure --without-x --enable-gui=no --with-tlib=ncurses
> >
> >I still got a lot of the same "Permission denied" errors. The
> >output of that command, beginning just before the first error is:
> >
> > checking for uint32_t... yes
> > checking whether time.h and sys/time.h may both be included... yes
> > checking for ino_t... yes
> > checking for dev_t... auto/configure: line 1933: conftest.c:
> > Permission denied
> > sed: can't read conftest.c: Permission denied
> > no
> > checking whether byte ordering is bigendian... auto/configure: line
> > 9532: conftest.c: Permission denied
> > sed: can't read conftest.c: Permission denied
> > auto/configure: line 9567: conftest.c: Permission denied
> > sed: can't read conftest.c: Permission denied
> > auto/configure: line 9614: conftest.c: Permission denied
> > sed: can't read conftest.c: Permission denied
> > auto/configure: line 9700: conftest.c: Permission denied
> > sed: can't read conftest.c: Permission denied
> > yes
> > checking for rlim_t... auto/configure: line 9756: conftest.c:
> > Permission denied
> > no
> > checking for stack_t... auto/configure: line 9792: conftest.c:
> > Permission denied
> > no
> > checking whether stack_t has an ss_base field... auto/configure:
> > line 9822: conftest.c: Permission denied
> > sed: can't read conftest.c: Permission denied
> > no
> > checking --with-tlib argument... ncurses
> > checking for linking with ncurses library... auto/configure: line
> > 9866: conftest.c: Permission denied
> > sed: can't read conftest.c: Permission denied
> > configure: error: FAILED
> >
> >I've never seen a "Permission denied" error from a configure script
> >before. I haven't investigated this further but thought someone
> >here might have seen this when building for Cygwin and already know
> >the solution.
> >
> >I'm running Cygwin 1.5.25 on a Windows XP system. Yes, I know 1.5
> >is obsolete, but I've been unable to get sshd working on other
> >Cygwin installations and I'm unwilling to risk breaking sshd on this
> >one by upgrading to 1.7.
> >
> >Regards,
> >Gary
> >
>
> Under what login name were you running this compile?
The same login name I always use, "Gary Johnson". (If I knew then
what I know now, I would not have used a name with a space.)
> Is it the same as the "owning username" shown by ls -l for the
> "permission denied" sources?
I forgot to mention that. I executed "find conftest.c" from the vim
directory--the directory containing .hg and the one from which I
executed "./configure ..."--and got no results, so I couldn't check
the permissions.
> Hadn't you changed it via su or sudo?
I never use su or sudo on Cygwin.
> What are these files' permissions as listed by ls -l ? (I would
> expect at least -rw-r--r-- or possibly, under Windows, -rwxr-xr-x)
As I wrote above, I couldn't check the permissions because the file
didn't exist after configure was done.
> Depending on your findings, the solution might involve either
> compiling under the correct username, or running chmod and/or
> chown recursively on the sources.
>From the vim directory I ran the following command:
$ find . | xargs ls -dl | grep -v 'Gary Johnson None'
So there are no files that are owned by other than user "Gary
Johnson" and group "None".
I could check configure to see if it ever explicitly checks anything
against my user name and see if it handles spaces properly. That's
a problem with rcs and some versions of ssh, so it might be a
problem with configure or some tool that it's using.
Note that the process I'm using worked fine through August, 2010, so
if it is something in configure it's something that has changed
since then.
Thank you and Ben for your suggestions.
Regards,
Gary
--
You received this message from the "vim_use" 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
