• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Leopard man pages
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Leopard man pages


  • Subject: Leopard man pages
  • From: Dan Korn <email@hidden>
  • Date: Tue, 18 Mar 2008 17:09:28 -0500

On Mar 18, 2008, at 4:40 PM, Peter O'Gorman wrote:
Dan Korn wrote:

That arch behaviour seems to be 10.5+ only.

Okay, actually, when I try that on my 10.5 machine, arch does allow me
to specify the architecture under which to run another command.
Interesting. However, the man page on Leopard still doesn't mention
anything about this capability, although if you give it just the "right"
invalid syntax (or "arch -h"), the usage will give you limited
information on this feature. Is this documented anywhere?

It is in the arch man page. Seems likely that you did an upgrade install
and still have the 10.4 manpage around. The leopard manpages are
compressed so the files do not overwrite the older ones at install time.

So, what you're telling me is that, in addition to of all the various architecture/OS/Xcode version combinations I have to worry about (PPC Tiger Intel Tiger, Intel Leopard with Xcode 2.5 and 3.0), there's now a difference between my Leopard machine which was upgraded from Tiger and a brand-new machine with Leopard installed? How am I possibly supposed to know this? And what other "surprise" differences don't I know about? How can I get my machine into a "full" Leopard state, short of wiping the hard drive and installing the OS again?


Or at least, what do I have to do to see the man pages for the utilities I'm actually running?

On Mar 18, 2008, at 4:35 PM, Jean-Daniel Dupas wrote:
Actually, doing "man arch" on Leopard give me this. Are you sure you man path does not contains some old man page.
In fact, I'm not sure that man search in the Developer directory by default. I think I have changed it the first time it returns me "no man" (by adding an xcode entry /etc/manpaths.d/).

Exactly what entry do I need to add, and where?

Thanks,
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


  • Follow-Ups:
    • Re: Leopard man pages
      • From: Jean-Daniel Dupas <email@hidden>
    • Re: Leopard man pages
      • From: Jonas Maebe <email@hidden>
References: 
 >Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: "Sherm Pendley" <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: "Sherm Pendley" <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: "Sherm Pendley" <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Jean-Daniel Dupas <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Graham J Lee <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Peter O'Gorman <email@hidden>)

  • Prev by Date: Re: Debugging Cocoa-Python
  • Next by Date: Re: Leopard man pages
  • Previous by thread: Re: Linking to third-party Frameworks and dylibs from a plug-in
  • Next by thread: Re: Leopard man pages
  • Index(es):
    • Date
    • Thread