I would let it go.
For some reason, I don't know why, Xcode pre 4.4 has decided that i386 kexts need something special that only the old linker can do. Unless you know specifically why, and you know that it's safe to do so, I would leave it alone. You said the output worked? If so, I'd recommend not worrying about it.
Avi Well, it seemed too simple to be true.
clang: warning: argument unused during compilation: '-classic_linker'
ld: framework not found NI488
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Any suggestions ?
On 27 août 2012, at 09:52, Jean Suisse wrote: I found the answer to my question in the source code file pointed by Jeff : -classic_linker is the one.
Cheers, Jean
On 27 août 2012, at 09:48, Jean Suisse wrote: Hi Jeff, Hi Avi
Thank you very much for your replies. I added the flags to use the new linker, and now the warning is gone.
If you upgrade to Xcode 4.4 then ld was taught the tricks that ld_classic had to use for i386 kexts and then you won't see that message. If you don't upgrade, the message is harmless.
Avi Well, actually, I can't upgrade to XCode 4.4, due to a framework issue.
But now I think about it, after some trials I was eventually stuck on a linker error… could it be so simple ? Do you know the reverse flag name ? I mean, how, to use the previous "old" linker on Xcode 4.4 ? (This issue is also the one tying me down to 10.7 btw)
Best regards, Jean
On 27 août 2012, at 03:27, Jeff Johnson wrote: Hi Jean.
You can make Xcode use the new linker with OTHER_LDFLAGS = "-Wl,-new_linker".
Here's the linker source code that prints the "using ld_classic" warning:
-Jeff
On Aug 26, 2012, at 2:36 PM, Jean Suisse wrote: Dear All,
When compiling my kext, I get the following warning :
ld: warning: using ld_classic
I know what ld_classic is. I guess there should be a replacement, but I don't know how to make Xcode use it. Anyway, my kext is working just fine, should I ignore this warning or further attempt to fix it ?
Best regards, Jean
|