I was just doinking around with the configure script to add an
--enable-profiling flag. I notice that "c++" is used to link my python.exe
(this on Mac OS X):
% make
c++ -Kthread -u __dummy -u _PyMac_Error -framework System -framework CoreServices -framework Foundation -o python.exe \
Modules/python.o \
libpython2.3.a -ldl
c++: unrecognized option `-Kthread'
case $MAKEFLAGS in \
*-s*) CC='gcc' LDSHARED='gcc -bundle -bundle_loader python.exe' OPT='-DNDEBUG -g -O3 -Wall -Wstrict-prototypes' ./python.exe -E ../setup.py -q build;; \
*) CC='gcc' LDSHARED='gcc -bundle -bundle_loader python.exe' OPT='-DNDEBUG -g -O3 -Wall -Wstrict-prototypes' ./python.exe -E ../setup.py build;; \
esac
running build
running build_ext
...
I probably would have missed it except for the fact that I was keeping my
eye on the emitted compile and link commands to see if there were problems.
Since when is c++ required to link the interpreter? Can someone verify this
problem?
Thx,
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4