On Wednesday, April 16, 2003, at 01:24 PM, Eric Long wrote: This list has helped me wrangle with some of the pitfalls with kernel extensions. Thanks to those who have provided input at various times. At present, I have a working kext for Jaguar. I'm now trying to create a version for 10.1.5. As far as I can tell, we should be able to support 10.1.5. At this point though, I'm encountering some "resistance". I found that the 2.9.5 GCC compiler used by PB, shipped with the 10.1.5 Dev tools, choked on the code. I think it should have been able to handle it, but it's not happy. For instance, I use a debugging macro with a variable arguments list, and it doesn't know how to handle it. It would be a nightmare for me to rewrite this code to suit that compiler. I was advised to obtain the April 2002 Dev tools, containing a pre-release version of PB that supports the GCC 3.1 compiler and that will run on 10.1.5. I obtained it and added the appropriate build setting to my project to compile with with GCC 3.1. The kext appears to build fine. Unfortunately, when I try to load it, I get a crop of undefined symbol errors Hi Eric, you can't build C++ for 10.1.5 using gcc 3.1. You have to use the older compiler. Aside from the typical version differences, the name-mangling changed for 3.1 and that's why you see all the undefined symbols. Note also that the commands used to load and unload kexts are quite different in 10.1.5. That's not a big deal but you'll have to re-do the finger-memory while you're testing. Regards.....Peter _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.
participants (1)
-
Peter Lovell