Jeremy Sanders kirjoitti:
Zooko Wilcox-O'Hearn wrote:
I'm not sure that you really need to explicitly invoke "g++" for
anything nowadays. Modern "gcc" notices that the input is C++ and
compiles it accordingly.
Could you be more specific about what doesn't work?
It does work, but prints out warnings:
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-
prototypes -fPIC -I/helpers/src -I/usr/include/qt4/QtCore -
I/usr/include/qt4/QtGui-I/usr/include/qt4 -I/usr/include/python2.6 -
Ihelpers/src -I/usr/include/python2.6 -c helpers/src/qtloops_helpers.cpp -o
build/temp.linux-i686-2.6/helpers/src/qtloops_helpers.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for
Ada/C/ObjC but not for C++
It would be nice if it didn't use invalid C++ options.
I'd like to be able to exactly specify the arguments to the compiler as Qt
requires particular options.
Jeremy
Compiling the extensions for pycryptopp also gives these kinds of warnings.
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
