Bill Janssen <[email protected]> wrote: > What is it, exactly, that's supposed to define _jcc_lib?
Ah, it's a command-line arg. And, in my build, I see that it is defined: gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp \ -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -Os -Wall \ -Wstrict-prototypes -DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -arch \ i386 -arch ppc -dynamiclib -D_jcc_lib -DJCC_VER="2.6" \ -I/System/Library/Frameworks/JavaVM.framework/Versions/Current/Headers \ -I_jcc -Ijcc/sources \ -I/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 \ -c jcc/sources/JCCEnv.cpp -o \ build/temp.macosx-10.5-i386-2.5/jcc/sources/JCCEnv.o -DPYTHON \ -fno-strict-aliasing -Wno-write-strings cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++ cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++ jcc/sources/JCCEnv.cpp: In member function ‘virtual void JCCEnv::reportException() const’: jcc/sources/JCCEnv.cpp:425: warning: unused variable ‘cls’ jcc/sources/JCCEnv.cpp: In member function ‘virtual void JCCEnv::reportException() const’: jcc/sources/JCCEnv.cpp:425: warning: unused variable ‘cls’ Bill
