fix tcl/tk version for debian 7.x
remove debugging print accidentally committed earlier
interp: no more static _setup

This patch is intended to make the interpreter lifecycle more controllable
and several independent interpreter instances per process possible

the arrays in interp_arrays.cc may remain static since they are read-only
and hence shareable between interpreter instances
interp: adapt exposure of _setup members

This employs the sledgehammer method of Python exposure: given a
verbose enough wrapper, anything can be exposed. There are
certainly ways to do this more elegant.

_setup.remaps remains unexposed for now - pretty sure the
introspect runtest was the only using code for this member
tests/interp: adapt remap/introspect

self.remaps not exposed for the time being
interp/setup_struct: add ctor, dtor declaration
interp/setup_struct: constructor definition
interp/Submakefile: add interp_setup.cc
build: add C++11 standard detection, CXXFLAGS autoconf support

this will add to CXXFLAGS without importing CFLAGS via Makefile.inc
which likely was by mistake

purpose: suppress warnings when compiling C++11 code
Merge remote-tracking branch 'origin/master' into unified-build-candidate-3

Conflicts:
	src/Makefile
	src/emc/rs274ngc/interp_array.cc
	src/emc/rs274ngc/rs274ngc_interp.hh
interp: fix interpretation of ambiguous "bind"

On some systems (at least ubuntu precise), the C++11 header <functional>
is indirectly included, which defines std::bind.  At this site, the
compiler selects this alternative instead of the socket primitive,
which can be unambiguously referred to as ::bind.
Avoid use of C++11 feature to initialize arrays and aggregates

Instead, use memset() to achieve initialization to all-bits-zero.
This is fine so long as the arrays and aggregates have only POD type.
interp: provide a constructor for block_struct

.. which can't be memset() due to having some non-POD members such as
remappings.
interp: rely on zero-arg constructor of setup_struct::blocks
axis: Don't directly use trp->result

This has been deprecated in Tcl for a very long time, and will
reportedly become a build error in Tcl 8.6. (sfbug#332)
emcsh: don't directly write to interp->result

This has been defined as not working for quite a long time.  It looks
like this routine is probably unused, but fix it anyway.  (sfbugs#332)
remove unused BITOPS_DEFINE
build: Enable C99, and no longer forbid declaration-after-statement

gcc has supported the C99 feature declaration-after-statement
since 3.0(!): http://gcc.gnu.org/gcc-3.0/c99status.html

as a result, any version of gcc plausibly being used today will support
this language feature at least when the relevant flag (i.e., -std=gnu99)
is passed and/or the relevant warning is silenced (i.e., -Wno-declaration-
after-statement)

In some versions of rtai, rtai_lxrt.h includes extern inlines which refer
to pthread functions.  We require that these function bodies not be
emitted into the object file when they are unused; this is accomplished
by the -fgnu89-inline flag, which uses the old inline behavior even when
c99/gnu99 mode is enabled.
Merge remote-tracking branch 'origin/master' into unified-build-candidate-3

Conflicts:
	src/Makefile
	src/rtapi/sim_rtapi_app.cc
rtapi_app: disambiguate bind()

seems this was triggered by the CXXFLAGS change (-std=c++0x being used)
only seen on gcc  4.6.3/wheezy/arm7l

see answer #1 http://stackoverflow.com/questions/14072009/error-using-algorithm-header-file-in-c