HI, 2008/2/9, Glynn Clements <[EMAIL PROTECTED]>: [snip] > I wouldn't assume that you can compile Python extensions without it. > > For simple libraries, it's enough to know what the header and library > files are called and to let the user specify where they can be found. > > For complex "subsystems", this is often inadequate. You may need any > number of additional libraries as well as specific compiler and linker > switches, many of which will be at least platform-dependent and > possibly worse (consider Gentoo, where everything gets built from > source with any number of user-selectable options). > > E.g. on my system: > > $ python-config --cflags > -I/usr/include/python2.4 -I/usr/include/python2.4 > -fno-strict-aliasing -DNDEBUG > > Okay, so --with-python-includes=-I/usr/include/python2.4 might > suffice, depending upon whether or not the code actually uses anything > which violates C aliasing rules and/or the extent to which the > compiler takes advantage of them (I presume the -fno-strict-aliasing > flag is there for a reason). > > But that's on my system. There's no telling what additional flags it > might need on some other system.
thanks for clarification, I modified the patch to require python-config (or python$PYVERSION-config), see http://trac.osgeo.org/grass/attachment/ticket/38/configure_wx-2.diff If no objections I will commit to SVN. Martin -- Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa * _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
