On 7/28/11 3:37 PM, Ryan Schmidt wrote:
On Jul 28, 2011, at 03:32, [email protected] wrote:
+AC_PATH_PROG(SWIG, [swig], [$PATH:/usr/local/bin])
+ @echo "Building ${SWIG_SRCS} requires swig, which you apparently did not have
installed when configuring MacPorts.">&2
+ @echo "Please install swig and re-run configure">&2
+ @echo "I recommend installing SWIG 1.x in /usr/local, because as of this writing
SWIG 2.x-generated code does not compile warning-free">&2
+ @echo "If you checked out from svn you can also run svn revert in
base/src/machista1.0 to get rid of this error">&2
Please please please no. We extremely do not want MacPorts users installing
anything in /usr/local. We constantly tell users not to do this because we
constantly receive bug reports from users who have things installed there which
are causing problems.
Yes, make a swig1 port fs you require swig 1.x and have swig1 be able to be
co-installed with swig.
Blair
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev