Hi,
If that is the case, we need to switch back to the dynamiclib
approach. Can you delete the 3 'sconstruct' script lines after "#
Catch Mac OS X and send the correct command line options to the
linker" and see if that works. Or try gcc with the '-dynamiclib' flag
(note that some of the other flags, although I'm not sure which, need
to be removed). It could be quite possible that the Fink Python 2.6
installation has removed the need for the bundle-loader approach :S
Cheers,
Edward
2009/8/17 Jack Howarth <howarth@xxxxxxxxxxxxxxxx>:
Edward,
Actually, I don't think the -bundle-loader approach will work
with python2.6 because it is linked against the libpython2.6 dylib
and not the static lib like python2.5. If you compare the symbols
returned fron "nm /sw/bin/python2.6" with "nm /sw/bin/python2.5",
the first case is a very short list...
0000200c D _NXArgc
00002008 D _NXArgv
U _PyMac_Error
U _Py_Main
00002000 D ___progname
00001fa8 t __dyld_func_lookup
00001000 A __mh_execute_header
00002004 D _environ
U _exit
00001fd0 T _main
00002010 d dyld__mach_header
00001f78 t dyld_stub_binding_helper
00001f30 T start
compared to the latter case. I really think we need to explicitly
link in /sw/lib/python2.6/config/libpython2.6.dylib.
Jack
On Mon, Aug 17, 2009 at 07:08:31PM +0200, Edward d'Auvergne wrote:
Hi,
I don't think this is an issue, as the include directories should only
contain *.h C header files. Can you find any *.h python files which
are not in /sw/include/python2.6? The second include directory is
just for the numpy *.h files.
Cheers,
Edward
Re: compiling 1.3.4 against python 2.6?