Broken man ????

superchink · 08-12-2002, 07:47 PM

wonder if anyone can help...

my man appears to be broken.

whenever i man [anything], i get the following output:

/usr/bin/man: illegal option -- C
man, version 1.1

usage: man [-adfhktw] [section] [-M path] [-P pager] [-S list]
[-m machine] [-p string] name ...

a : find all matching entries
d : print gobs of debugging information
f : same as whatis(1)
h : print this help message
k : same as apropos(1)
t : use troff to format pages for printing
w : print location of man page(s) that would be displayed

M path : set search path for manual pages to `path'
P pager : use program `pager' to display pages
S list : colon separated section list
m machine : search for alternate architecture man pages
p string : string tells which preprocessors to run
e - [n]eqn(1) p - pic(1) t - tbl(1)
g - grap(1) r - refer(1) v - vgrind(1)

nkuvu · 08-12-2002, 07:54 PM

Have you set any aliases to man? Or any environment variables to add to man?

Obviously something is setting the C option, which is not a valid option.

Modified any login files recently?

superchink · 08-12-2002, 09:49 PM

Not that i know of. Is there any way to check environment variables? like a centralized location?

pmccann · 08-13-2002, 12:41 AM

To see your current environment variables enter

% printenv

To see what "less" means in your current session look at

% echo $less

That might be empty ("undefined variable"). You might have it set up as an alias: to check that use

% alias less

and see if you get any non-trivial output. You can unalias it for the
current session using

% unalias less

but of course you'd like to do so more comprehensively. If you're using
tcsh as your shell you'll probably want to peruse ~/.cshrc, ~/.tcshrc if you've
got one, and the central files in /etc/share/init/tcsh. To find what you're looking for in there just grep for "less" and peck through the output for suspicious lines:

% cd /usr/share/init/tcsh
% grep less *

Best of luck,
Paul

sao · 08-13-2002, 02:16 AM

superchink,

Could you check:

What version of make? ('make -v')

What does a "ls -la /usr/bin/make" give?

Code:

151 [Sao @/Users/pm] % ls -la /usr/bin/make
lrwxr-xr-x    1 root     wheel           7 Jul  2 20:43 /usr/bin/make -> gnumake

<<make: illegal option -- C>>

"You've replaced the GNU version of the make utility installed as part of the Developer Tools with a BSD version of make. Many packages rely on special features only supported by GNU make.
Make sure that /usr/bin/make is a symlink to gnumake, not bsdmake. Furthermore, make sure that /usr/local/bin/ does not contain another copy of make".

Check the same for man.

ls -la /usr/bin/man

ls -la `which man`

Let me know.

Cheers...

mervTormel · 08-13-2002, 03:31 AM

uh, my man takes the -C switch and spits different usage than yours...

Code:

$ which man
/usr/bin/man

$ man
usage: man [-achw] [-C file] [-M path] [-m path] [section] title ...

$ man -z
man: illegal option -- z
usage: man [-achw] [-C file] [-M path] [-m path] [section] title ...

so, i think man v1.1 is a miscreant here. i don't know where you got your man installed in /usr/bin/ but it ain't the one i got.

and i don't see how make is involved here; man is dist'd binary with OSX, no?

so, superchink, where'd you get man v1.1 ? have you been installing 3rd party reprobate packages that have stomped on the system's binaries?

and what is loading man with the -C switch? have you mucked in /etc/man.conf?

it seems like there could be an alias frobbing the works. but, that ain't the man you want, i don't think.

what say you?

superchink · 08-13-2002, 03:52 AM

OK, simple solution.

% which man

told me it was using /sw/bin/man

(FINK)

the bastards...

so i just commetned out the init in my .cshrc file to /sw/bin/init.csh

and voila.

no more man problems.

(god that sounds gay...)

thanks for the help.

mervTormel · 08-13-2002, 03:53 AM

aha! man v1.1 is from jaguar. superchink, you've been made and we've been had.

Code:

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.2
BuildVersion:   6C115

$ man -C
man: illegal option -- C
man, version 1.1

usage: man [-adfhktw] [section] [-M path] [-P pager] [-S list]
           [-m machine] [-p string] name ...

  a : find all matching entries
  d : print gobs of debugging information
  f : same as whatis(1)
  h : print this help message
  k : same as apropos(1)
  t : use troff to format pages for printing
  w : print location of man page(s) that would be displayed

  M path    : set search path for manual pages to `path'
  P pager   : use program `pager' to display pages
  S list    : colon separated section list
  m machine : search for alternate architecture man pages
  p string : string tells which preprocessors to run
               e - [n]eqn(1)   p - pic(1)    t - tbl(1)
               g - grap(1)     r - refer(1)  v - vgrind(1)

that little difference makes a lot of difference. unsupported

mervTormel · 08-13-2002, 03:55 AM

what?! yer initial post says /usr/bin/man ...

yer renegade, man

sao · 08-13-2002, 05:48 AM

MervTormel,

Sorry, I didn't explain it clearly.

Quote:


	MervTormel wrote: and i don't see how make is involved here; man is dist'd binary with OSX, no?

I just wrote about make as an example. Because the same happens if you have two versions of make and Fink installed. Which I suspected he had.

That's why I asked him to check the same for 'man'

He figure it out by himself.

Code:

151 [Sao @/Users/pm] % ls -la `which man`
-rwxr-xr-x    1 root     unknown     60256 Aug  5 06:42 /sw/bin/man

Cheers...

pmccann · 08-13-2002, 09:22 AM

Hmm, this has to be one of the most bizarre threads I've seen:

Superchink comes in complaining about a bad man.

Some raving idiot starts rambling on about less (than usual).

Sao comes riding in to "make" the peace/piece.

MervTormel rolls up to our bumper in his long black (Jaguar) limousine, offering a good dose of (a)version therapy.

Then, just to nail the thing shut, Superchink reveals the sad truth. He's finked on us, and is now trying to protect his arse. (Use a bin, man, use a bin..)

Communication: gotta love it.

Cheers,
Paul

sao · 08-13-2002, 10:34 AM

pmccann,

Thanks for the laughs

Cheers...

PS:

superchink · 08-13-2002, 03:54 PM

just for the record, that's the only problem i've had w/ jaguar yet.

i can live with it.

haha.

sao · 08-14-2002, 12:53 AM

superchink,

Was your fink installation there prior to installing Jaguar, or you installed after Jaguar?

What version of the Developer Tools Jaguar installs? ('cc -v')

Could you test to install some packages?

Thanks.

Cheers...

superchink · 08-14-2002, 12:56 PM

the fink install was PRIOR to the Jaguar install.

I do believe I had installed that beta (?) version of the dev tools. I'm not booted on my HD at the moment so I am unable to check those things right now. But sure, i can test packages if you'dd like. lemme know..

sao · 08-14-2002, 11:30 PM

Well, I thought Jaguar would install new developer tools.

Yes, if you could gives us feedback on some new Fink installs that would be very welcome.

Thanks.

Cheers...

08-12-2002, 07:47 PM	#1
superchink Prospect Join Date: Aug 2002 Posts: 5	Broken man ???? wonder if anyone can help... my man appears to be broken. whenever i man [anything], i get the following output: /usr/bin/man: illegal option -- C man, version 1.1 usage: man [-adfhktw] [section] [-M path] [-P pager] [-S list] [-m machine] [-p string] name ... a : find all matching entries d : print gobs of debugging information f : same as whatis(1) h : print this help message k : same as apropos(1) t : use troff to format pages for printing w : print location of man page(s) that would be displayed M path : set search path for manual pages to `path' P pager : use program `pager' to display pages S list : colon separated section list m machine : search for alternate architecture man pages p string : string tells which preprocessors to run e - [n]eqn(1) p - pic(1) t - tbl(1) g - grap(1) r - refer(1) v - vgrind(1)

08-13-2002, 02:16 AM	#5
sao Moderator Join Date: Jan 2002 Location: Singapore Posts: 4,237	superchink, Could you check: What version of make? ('make -v') What does a "ls -la /usr/bin/make" give? Code: 151 [Sao @/Users/pm] % ls -la /usr/bin/make lrwxr-xr-x 1 root wheel 7 Jul 2 20:43 /usr/bin/make -> gnumake <<make: illegal option -- C>> "You've replaced the GNU version of the make utility installed as part of the Developer Tools with a BSD version of make. Many packages rely on special features only supported by GNU make. Make sure that /usr/bin/make is a symlink to gnumake, not bsdmake. Furthermore, make sure that /usr/local/bin/ does not contain another copy of make". Check the same for man. ls -la /usr/bin/man ls -la `which man` Let me know. Cheers... Last edited by sao; 08-13-2002 at 02:41 AM.

08-13-2002, 03:31 AM	#6
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	uh, my man takes the -C switch and spits different usage than yours... Code: $ which man /usr/bin/man $ man usage: man [-achw] [-C file] [-M path] [-m path] [section] title ... $ man -z man: illegal option -- z usage: man [-achw] [-C file] [-M path] [-m path] [section] title ... so, i think man v1.1 is a miscreant here. i don't know where you got your man installed in /usr/bin/ but it ain't the one i got. and i don't see how make is involved here; man is dist'd binary with OSX, no? so, superchink, where'd you get man v1.1 ? have you been installing 3rd party reprobate packages that have stomped on the system's binaries? and what is loading man with the -C switch? have you mucked in /etc/man.conf? it seems like there could be an alias frobbing the works. but, that ain't the man you want, i don't think. what say you?

08-12-2002, 07:54 PM	#2
nkuvu MVP Join Date: Jun 2002 Location: Tucson, Arizona Posts: 1,236	Have you set any aliases to man? Or any environment variables to add to man? Obviously something is setting the C option, which is not a valid option. Modified any login files recently?

08-12-2002, 09:49 PM	#3
superchink Prospect Join Date: Aug 2002 Posts: 5	Not that i know of. Is there any way to check environment variables? like a centralized location?

08-13-2002, 12:41 AM	#4
pmccann Major Leaguer Join Date: Jan 2002 Location: Adelaide, South Australia Posts: 470	To see your current environment variables enter % printenv To see what "less" means in your current session look at % echo $less That might be empty ("undefined variable"). You might have it set up as an alias: to check that use % alias less and see if you get any non-trivial output. You can unalias it for the current session using % unalias less but of course you'd like to do so more comprehensively. If you're using tcsh as your shell you'll probably want to peruse ~/.cshrc, ~/.tcshrc if you've got one, and the central files in /etc/share/init/tcsh. To find what you're looking for in there just grep for "less" and peck through the output for suspicious lines: % cd /usr/share/init/tcsh % grep less * Best of luck, Paul

08-13-2002, 03:52 AM	#7
superchink Prospect Join Date: Aug 2002 Posts: 5	OK, simple solution. % which man told me it was using /sw/bin/man (FINK) the bastards... so i just commetned out the init in my .cshrc file to /sw/bin/init.csh and voila. no more man problems. (god that sounds gay...) thanks for the help.

08-13-2002, 03:55 AM	#9
mervTormel League Commissioner Join Date: Jan 2002 Posts: 5,536	what?! yer initial post says /usr/bin/man ... yer renegade, man

08-13-2002, 09:22 AM	#11
pmccann Major Leaguer Join Date: Jan 2002 Location: Adelaide, South Australia Posts: 470	Hmm, this has to be one of the most bizarre threads I've seen: Superchink comes in complaining about a bad man. Some raving idiot starts rambling on about less (than usual). Sao comes riding in to "make" the peace/piece. MervTormel rolls up to our bumper in his long black (Jaguar) limousine, offering a good dose of (a)version therapy. Then, just to nail the thing shut, Superchink reveals the sad truth. He's finked on us, and is now trying to protect his arse. (Use a bin, man, use a bin..) Communication: gotta love it. Cheers, Paul

08-13-2002, 10:34 AM	#12
sao Moderator Join Date: Jan 2002 Location: Singapore Posts: 4,237	pmccann, Thanks for the laughs Cheers... PS:

08-13-2002, 03:54 PM	#13
superchink Prospect Join Date: Aug 2002 Posts: 5	just for the record, that's the only problem i've had w/ jaguar yet. i can live with it. haha.

08-14-2002, 12:53 AM	#14
sao Moderator Join Date: Jan 2002 Location: Singapore Posts: 4,237	superchink, Was your fink installation there prior to installing Jaguar, or you installed after Jaguar? What version of the Developer Tools Jaguar installs? ('cc -v') Could you test to install some packages? Thanks. Cheers...

08-14-2002, 12:56 PM	#15
superchink Prospect Join Date: Aug 2002 Posts: 5	the fink install was PRIOR to the Jaguar install. I do believe I had installed that beta (?) version of the dev tools. I'm not booted on my HD at the moment so I am unable to check those things right now. But sure, i can test packages if you'dd like. lemme know..

08-14-2002, 11:30 PM	#16
sao Moderator Join Date: Jan 2002 Location: Singapore Posts: 4,237	Well, I thought Jaguar would install new developer tools. Yes, if you could gives us feedback on some new Fink installs that would be very welcome. Thanks. Cheers...