Apple

On Thu, Apr 10, 2014 at 2:25 AM, Jeremy Kezer <email@hidden> wrote:

Unfortunately, the original author of the kext is no longer around, and I'm a bit of a neophyte with kexts. Also, our code isn't directly referencing the extended commands that are being complained about but is using the base configRead8 etc. But our non-extended calls are definitely the cause of these errors; if I comment our use of configRead8 the extendedConfigRead8 errors disappear.

configRead8 etc. are defined inline in the header and call down to the extended* versions directly, so it makes sense that those functions would be inlined in your kext as direct calls to the extended functions.

Why it's failing to link is less clear.

To try and see if this was an isolated problem to our kext, I added some calls to the AppleSamplePCI sample project (in such a way that they would not actually be executed but not stripped), and it worked fine. More head scratching ensued.

If I go back to Xcode 5.0.2, everything is fine.

I've had similar cases of spurious kext link errors in the past. They have always been down to linker arguments that were added manually or were inherited from an old Xcode version's project file. The fact that a fresh project doesn't have the problem leads me to think that might be the problem here too. I suggest comparing the linker and compiler command lines from the clean project with the one that's causing problems. I would expect there to be some discrepancy, and you can divide-and-conquer to track down the problem from there.

References:
	>Kext loading errors after building with Xcode 5.1 (From: Jeremy Kezer <email@hidden>)