Re: Leopard man pages
Re: Leopard man pages
- Subject: Re: Leopard man pages
- From: Dan Korn <email@hidden>
- Date: Tue, 18 Mar 2008 18:21:49 -0500
On Mar 18, 2008, at 5:29 PM, Jonas Maebe wrote:
You could have been aware of it by reading various Apple mailing
lists and/or Apple-related web sites, but nobody expects you to know
about all bugs in a particular Mac OS X version or its install
process. That's the nature of bugs...
Right. Sorry to fill up the list with complaints; it's been a
frustrating process doing yet another port for Mac. Finding out all
this stuff the hard way, especially when I'm trying to be diligent
about searching for stuff and figuring it out myself, compounds that.
I am trying to follow along, although I admit that I'm not a full-time
Mac developer, so I can't be as devoted as some.
And what other "surprise" differences don't I know about?
You can always Google for "leopard upgrade issues" or similar.
Yes, Google is our friend, but that particular search mostly turns up
issues that appear immediately at the time of the upgrade, like the
Mac Blue Screen of Death. And like anything else, most of the stuff
is not developer-centric. I love *using* Mac and Leopard; it's
developing for them that's giving me headaches.
Or at least, what do I have to do to see the man pages for the
utilities I'm actually running?
http://forums.macosxhints.com/showthread.php?t=80171&page=3
Hmm. That page seems to be specific to X11, and relies on a Ruby
script. I followed the instructions at the end of this page instead,
which seem a bit more succinct and reversible:
http://www.macosxhints.com/article.php?story=20071201021830891
Specifically:
sudo mkdir /usr/share/man/old
sudo find /usr/share/man -type f -exec test -e {}.gz \; -exec mv {} /
usr/share/man/old \;
sudo find /usr/share/man -type l -exec test -e {}.gz \; -exec mv {} /
usr/share/man/old \;
Now when I do "man arch", I get the information about the arguments.
Yay! Hopefully that's all I need to do to get in synch.
On Mar 18, 2008, at 5:35 PM, Jean-Daniel Dupas wrote:
If you have install "UNIX Development Support" with Xcode (that is
all optional stuff copied in /usr) you don't have to change anything
as man page are already in /usr/share/man, but if you don't have,
you can add a file with any name in "/etc/manpaths.d/" with one
single line:
/Developer/usr/share/man
Thanks. Prepending that to my MANPATH would probably have worked, but
I already ran the script above, and I seem to be getting the right
info now.
(i assume Xcode 3 is install in /Developer, but if this is not the
case, adjust this line)
Actually, I have both Xcode 2.5 and 3.0 installed, so I do have that
folder, but I also have an /Xcode2.5/usr/share/man/ folder. It looks
like they contain basically the same things, though. At any rate, if
I understand things correctly, I think that the utilities installed
with Leopard's "UNIX Development Support" package are the same ones
installed with Xcode 3.0. If not, it seems like I want to use the man
pages at /usr/share/man to go with the utilities at /usr/bin et al
anyway.
About the problem with old man pages. Xcode does not really like
updates. The only reliable way to update it is to uninstall the
current version, and install then new one, else there is always some
minor issus like this one. So I don't know how to get a "full"
Leopard state.
I think it's not just Xcode that doesn't like the updates; the Leopard
upgrade affects my Unix development environment, even if I'm not using
Xcode. So does the Xcode upgrade, for that matter. Although like I
said, I'm not trying to do any actual Unix development. But the
command-line tools are certainly handy, and in some cases (like
modifying dynamic library loading paths), indispensable.
Thanks again,
Dan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden