• 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
Reliable way to determine bitness of the kernel
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Reliable way to determine bitness of the kernel


  • Subject: Reliable way to determine bitness of the kernel
  • From: eveningnick eveningnick <email@hidden>
  • Date: Tue, 22 Feb 2011 10:09:08 -0800

hello
i have a kext (or, rather, 2 kexts - one built with -arch i386, another one
with -arch x86_64). They should work on both OS X 10.5 and 10.6.
i have an installing script, which looks like
if [ `uname -a | grep x86_64 | wc -l` ge 1 ]; then
   cp -R "64bit.kext" "/Library/Extensions/"
else
   cp -R "32bit.kext" "/Library/Extensions/"

this goes into production code.
But unfortunately, it seems like it does not work well on all systems.
What caveats may this method of determining the bitness of the system have?
It works fine on my Leopard and Snow Leopard (even though my Snow Leo runs
in 32 bit mode), but other people complain that the driver is not being
installed.
Maybe some instances of the system are missing any of the command line
utilities i used?
Could you suggest a better way of determining the bitness of the kernel?
Thanks for any advice!
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Reliable way to determine bitness of the kernel
      • From: Dave Zarzycki <email@hidden>
    • Re: Reliable way to determine bitness of the kernel
      • From: Wim Lewis <email@hidden>
  • Prev by Date: Re: Accessing a managedObject property from within an accessor of another property
  • Next by Date: Re: Accessing a managedObject property from within an accessor of another property
  • Previous by thread: Re: Problem opening file
  • Next by thread: Re: Reliable way to determine bitness of the kernel
  • Index(es):
    • Date
    • Thread