Re: configure.in question: compiler but not ld flags

From what I can tell, the source of the problem is what Apple calls "toll-free" bridging, which is cast-equivalency between C-language Core Foundation datatypes (most of which start with CF) and their Foundation Kit (objective-c) equivalents.

Whether it's proper or not (and I agree that there seems to be some over-reaching in the headers), it's what I need to be able to do. Thus, it seems that there ought to be a way to specify an option for the compile phase and not linking. Truth be told, it's only really necessary for backend.cmod, but that's probably beside the point.

Sounds like a way around the problem could be to make some minimal Objective-C glue that the cmod could interface with in turn.