On Tue, Jul 13, 2010 at 6:14 AM, stephane eranian <eran...@googlemail.com> wrote: > On Thu, Jun 24, 2010 at 8:18 PM, Corey Ashford > <cjash...@linux.vnet.ibm.com> wrote: >> On 06/24/2010 06:45 AM, Dan Terpstra wrote: >>> >>> Why do you need to install swig? >>> If we have no intention to use a scripting language for libpfm4, should it >>> be required that a default build have swig? This seems like an unnecessary >>> constraint placed on the build environment. I'd rather see the python stuff >>> built optionally with a command line argument or an environment variable or >>> something. >>> - d >> >> Either that, or detect the error during the make and generate a useful error >> message like: >> >> "In order to build the Python interface, you need to have swig installed. >> Or you can choose not to build the Python interface >> by adding NO_PYTHON=1 to the make invocation." >> > Maybe we should default to python off. I think you can detect the presence > of swig without autoconf. They do a lot of that in the Makefile for perf. > I forgot to say that if you have a patch, I'd be happy to merge it in!
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
