Xcode 4.6.2 and code sign for 32/64 bit FAT kext

  • Xcode 4.6.2 is generating invalid binaries for a 32/64bit kernel extensions.  The error reported from kextutil (on a 32 bit system) is:

      (kernel) kxld[<bundleid>]: The Mach-O file is malformed: Invalid segment type in MH_OBJECT kext: 29.

    I can work around this by disabling code signing for the extension. However, is there a way to persuade codesign to work correctly for the FAT binary?  I have tried adding the "--no-macho" command line switch, but to no avail.

    This affects any system with a 32 bit kernel (including 10.7, which I believe is still supported).

    Any help would be appreciated... at the moment I have to either ditch code signing or revert to Xcode 4.4 to avoid the problem.

    -- Mark
  • On Fri, 17 May 2013 19:00:43 +0200, Mark Moore said:

    > Xcode 4.6.2 is generating invalid binaries for a 32/64bit kernel
    > extensions.  The error reported from kextutil (on a 32 bit system) is:
    >
    > (kernel) kxld[<bundleid>]: The Mach-O file is malformed: Invalid
    > segment type in MH_OBJECT kext: 29.
    >
    > I can work around this by disabling code signing for the extension.
    > However, is there a way to persuade codesign to work correctly for the
    > FAT binary?  I have tried adding the "--no-macho" command line switch,
    > but to no avail.
    >
    > This affects any system with a 32 bit kernel (including 10.7, which I
    > believe is still supported).
    >
    > Any help would be appreciated... at the moment I have to either ditch
    > code signing or revert to Xcode 4.4 to avoid the problem.

    That seems to be addressed in the release notes:

    <http://developer.apple.com/library/ios/#releasenotes/DeveloperTools/RN-Xcod
    e/index.html
    >

    Cheers,

    --
    ____________________________________________________________
    Sean McBride, B. Eng                <sean...>
    Rogue Research                        www.rogue-research.com
    Mac Software Developer              Montréal, Québec, Canada
  • Thanks - I was hoping for something more practical.  I think that for now we are just going to disable code-signing, and hope for a forthcoming fix from Apple.

    -- Mark

    On 17 May 2013, at 19:05, "Sean McBride" <sean...> wrote:

    > That seems to be addressed in the release notes:
    >
    > <http://developer.apple.com/library/ios/#releasenotes/DeveloperTools/RN-Xcod
    e/index.html
    >
    >
    > Cheers,
    >
    > --
    > ____________________________________________________________
    > Sean McBride, B. Eng                <sean...>
    > Rogue Research                        www.rogue-research.com
    > Mac Software Developer              Montréal, Québec, Canada
    >
    >
previous month may 2013 next month
MTWTFSS
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
Go to today