This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Another (differently) broken man on CygWin 1.5.8 -- Apropos still troublesome


> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Eric Blake
> Sent: Monday, August 15, 2005 10:01 AM
> To: Herb Martin; cygwin@cygwin.com
> Subject: RE: Another (differently) broken man on CygWin 1.5.8 
> -- Apropos still troublesome
> 
> > There is a man directory in /usr/bin, i.e., /usr/bin/man -- with 
> > man.exe being the program, while manpath gives:
> 
> This sentence was confusing.  Are you telling me that 
> /usr/bin/man exists and is a directory (does it have normal 
> subdirectories like man1?), 

Yes, that WAS the situation until I copied the contents to
another man directory and renamed this subdirectory to fix
the problem.

> ...and that /usr/bin/man.exe exists 
> and is the program?  

Yes.  Precisely.

> I'm trying to see if there is anything 
> weird about auto-.exe magic in coreutils.

I believe that I get the gist of this, adn (see
below) don't think there is a auto-.exe magic 
problem UNLESS it is supposed to work even in the
presence of a directory with a conflicting name.
-- and if I can help let me know.

I do NOT remember creating that directory but it is 
possible that I did so when trying to make ClamAV 
help work at some point.
	

> > 
> > $ manpath
> > 
> /usr/local/man:/usr/share/man:/usr/man:/usr/X11R6/man:/usr/ssl/man:/us
> > r/X11R
> > 6/share/man
> > 
> > $ which apropos
> > /usr/bin/apropos
> > 
> > $ link /usr/bin/man.exe /usr/bin/man
> > link: cannot create link `/usr/bin/man' to `/usr/bin/man.exe': File 
> > exists
> 
> What were you trying here - to create /usr/bin/man as an 
> alternate spelling of man.exe?  Would 'ln -f' work better 
> than 'link' did?  link(1) currently does not do extra .exe 
> magic, only ln(1).  I'll have to check if
> ln(1) has problems if the non-.exe version exists as a 
> directory, and decide whether link(1) should do .exe magic...

Yes, but I now understand the problem to be due to "man"
subdirectory existing, not the failure of the "man vs. man.exe"
magic.  (Which is likely what you were referencing above with
the auto-.exe magic comment.)

As to the link, I was trying to sweep the problem under the
rug since I didn't know a fix for it.  (All works now without
the ./man subdirectory to conflict with man.exe in that same
directory.

> > $ which man.exe
> > /usr/bin/man.exe
> > 
> > Man works, but I cannot build a link from man->man.exe due to the 
> > directory with the same name:
> > 
> > $ man
> > What manual page do you want?
> > 
> > Running hash against /usr/bin/man without adding the .exe 
> fails this 
> > way:
> > 
> > $ hash -p /usr/bin/man man
> > bash: hash: /usr/bin/man: Is a directory
> > 
> > This seems to work but doesn't fix apropos:
> > $ hash -p /usr/bin/man.exe man
> > bash: hash: /usr/bin/man: Is a directory
> > 
> 
> That is sounding a bit weird.  I'll have to see if I can 
> reproduce that, and if it implies a bug in bash's hashing.  
> No guarantees of when, though, since it seems you've solved 
> your problem by getting rid of the /usr/bin/man/ directory.

/usr/bin had both:

	/usr/bin/man.exe
	/usr/bin/man		(subdirectory tree) 
			./man1
			./man5
			./man8

Should be trivial to test if that behavior is not
expected.

--
Herb 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]