Xcode 5 removed support for building 32-bit kexts

Originator:SelfTransformingElfMachine
Number:rdar://15292945 Date Originated:22-Oct-2013 04:30 PM
Status:Open Resolved:
Product:Xcode Product Version:5
Classification: Reproducible:
 
Summary:
Xcode 5 can no longer build 32-bit kernel extensions.

Steps to Reproduce:
1. Install Xcode 5
2. Build a universal 32/64 bit kext
3. Profit!

Expected Results:
A universal binary kext with 32 and 64 bit architectures.

Actual Results:
32 bit fails to build with "clang: error: the clang compiler does not support 'fapple-kext' for C++ on Darwin/i386"

Version:
Xcode 5 (moving up from Xcode 4)

Notes:
Is there a supported way to add the clang 4.0 toolchain from Xcode 4.x to Xcode 5?

Configuration:
Model Name:  iMac
Model Type:  27-inch, Late 2012
Model Identifier:  iMac13,2
Processor Name:  Intel Core i7 CPU 3770
Processor Model:  Ivy Bridge
Processor Speed:  3.4 GHz
Number of Processors:  1
Total Number of Cores:  4
Memory Size:  16 GB 1600 MHz DDR3
Graphics Model:  NVIDIA GeForce GTX 680MX 2048 MB
Assembled in:  China
Manufactured during:  June 2013
Serial Number: 
L1 Cache:  64 KB
L2 Cache:  256 KB (per Core)
L3 Cache:  8 MB
Processor Bitrate:  64 bit
EFI Bitrate:  64 bit
Kernel Bitrate:  64 bit
Direct Media Interface:  5.0 GT/s
Boot ROM Version:  IM131.010A.B05
System SMC Version:  2.11f16
Power Source:  AC Power.
Hardware Universal Unique Identifier:  1525912F-5A88-5E7C-9A35-0476CBF1BD43
Minimum Supported Operating System:  OS X 10.8.2 (Build 12C2037) (Mountain Lion)
Current Boot Operating System:  OS X 10.8.4 Build 12E55 (Mountain Lion)
Maximum Supported Operating System:  Latest version of OS X 10.8 (Mountain Lion)


Attachments:


Xcode 4 does not work on 10.9 Mavericks because of crashes in ibtoold and hanging during lipo "Create universal binary <target>".

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!