rtapi/rtapi_task.c:  silence -Wunused-but-set-variable warnings

    rtapi/rtapi_task.c: In function ‘_rtapi_task_new’:
    rtapi/rtapi_task.c:117:9: warning: variable ‘retval’ set but not used
        [-Wunused-but-set-variable]
	     int retval = 0;
		 ^
machinetalk/lib/mk_backtrace.c:  fix `syminfo_callback` declaration

    machinetalk/lib/mk_backtrace.c: In function ‘full_callback’:
    machinetalk/lib/mk_backtrace.c:62:7: warning: passing argument 3 of
       ‘backtrace_syminfo’ from incompatible pointer type [enabled by default]
	   error_callback, data);
	   ^
    In file included from machinetalk/lib/mk_backtrace.c:15:0:
    /usr/lib/gcc/x86_64-linux-gnu/4.8/include/backtrace.h:190:12: note:
        expected ‘backtrace_syminfo_callback’ but argument is of type
	‘void (*)(void *, uintptr_t,  const char *, uintptr_t,  uintptr_t)’
	     extern int backtrace_syminfo (struct backtrace_state *state
			^
machinetalk/support/unionread.c:  silence multiple compiler warnings

Silence `-Wformat=` warning printing `uint64_t`.

Silence `-Wunused-variable' warning by disabling code related to
another block of disabled code.  :P

    machinetalk/support/unionread.c: In function ‘print_container’:
    machinetalk/support/unionread.c:61:5: warning: format ‘%llu’ expects
        argument of type ‘long long unsigned int’, but argument 2 has type
	‘uint64_t’ [-Wformat=]
	     printf("submessage length=%llu\n", length);
	     ^
    machinetalk/support/unionread.c:41:10: warning: unused variable ‘eof’
        [-Wunused-variable]
	     bool eof;
		  ^
rtapi/rtapi_app.cc: silence -Wformat-security warnings

    rtapi/posix/rtapi_app.cc: In function ‘int mainloop(size_t, char**)’:
    rtapi/posix/rtapi_app.cc:933:44: warning: format not a string literal
      and no format arguments [-Wformat-security]
	  if ((z_port = zsocket_bind(z_command, uri )) < 0) {
						    ^
hal/lib/hal_lib.c:  silence -Wformat-security warnings

    hal/lib/hal_lib.c: In function ‘hal_print_msg’:
    hal/lib/hal_lib.c:3707:5: warning: format not a string literal and no
        format arguments [-Wformat-security]
	     rtapi_print_msg(level, _hal_errmsg);
	     ^
.../webtalk/webtalk_defaultpolicy.cc:  silence -Wformat-security warnings

    machinetalk/webtalk/webtalk_defaultpolicy.cc: In function
        ‘int default_policy(wtself_t*, zws_session_t*, zwscb_type)’:
    machinetalk/webtalk/webtalk_defaultpolicy.cc:125:41: warning: format
        not a string literal and no format arguments [-Wformat-security]
	    if (zsocket_connect (wss->socket, uri)) {
						 ^
    machinetalk/webtalk/webtalk_defaultpolicy.cc:138:46: warning: format
        not a string literal and no format arguments [-Wformat-security]
	    if (zsocket_connect (wss->socket, q->value)) {
						      ^
    machinetalk/webtalk/webtalk_defaultpolicy.cc:147:46: warning: format
        not a string literal and no format arguments [-Wformat-security]
	   if (zsocket_bind (wss->socket, q->value) < 0) {
						  ^
machinetalk/haltalk/haltalk_main.cc:  silence -Wformat-security warnings

    machinetalk/haltalk/haltalk_main.cc: In function ‘int zmq_init(htself_t*)’:
    machinetalk/haltalk/haltalk_main.cc:174:76: warning: format not a string
      literal and no format arguments [-Wformat-security]
	 self->z_group_port = zsocket_bind(self->z_halgroup,
	    self->cfg->halgroup);
			       ^
    machinetalk/haltalk/haltalk_main.cc:185:76: warning: format not a string
      literal and no format arguments [-Wformat-security]
	 self->z_rcomp_port = zsocket_bind(self->z_halrcomp,
	    self->cfg->halrcomp);
			       ^
    machinetalk/haltalk/haltalk_main.cc:198:77: warning: format not a string
      literal and no format arguments [-Wformat-security]
	 self->z_halrcomp_port = zsocket_bind(self->z_halrcmd,
	    self->cfg->command);
			      ^
hal/cython/machinekit/rtapi.pyx: silence -Wformat-security warnings

    hal/cython/machinekit/rtapi.c: In function
      ‘__pyx_pf_5rtapi_11RTAPILogger_2write’:
    hal/cython/machinekit/rtapi.c:2222:3: warning: format not a string
      literal and no format arguments [-Wformat-security]
	 rtapi_print_msg(__pyx_v_self->_level, __pyx_t_3);
	 ^
rtapi/rtapi_msgd.cc:  fix -Wformat-security warnings

    rtapi/rtapi_msgd.cc: In function ‘int main(int, char**)’:
    rtapi/rtapi_msgd.cc:993:50: warning: format not a string literal and
      no format arguments [-Wformat-security]
	 logpub_port = zsocket_bind(logpub, logpub_uri);
						      ^
hal/utils/halcmd_rtapiapp.cc: silence -Wformat-security warnings

    hal/utils/halcmd_rtapiapp.cc: In function
      ‘int rtapi_connect(int, char*, const char*)’:
    hal/utils/halcmd_rtapiapp.cc:206:39: warning: format not a string
      literal and no format arguments [-Wformat-security]
	 if (zsocket_connect(z_command, uri)) {
					   ^
Fix my mistake in hal/drivers/mesa-hostmot2/watchdog.c

Oops.  A good case for heeding warnings.

    .../hal/drivers/mesa-hostmot2/watchdog.c: In function
        ‘hm2_watchdog_force_write’:
    .../hal/drivers/mesa-hostmot2/watchdog.c:319:47: warning: value computed
        is not used [-Wunused-value]
	     do_div(tmp,(u64)(1000 * 1000 * 1000)) - 1;
						   ^
src/rtapi/rtapi_shmem.c:  silence -Wformat= warning

`printf` length modifer and flag for type `size_t` is `%zu`.

    .../rtapi/rtapi_shmem.c: In function ‘_rtapi_shmem_delete_inst’:
    .../rtapi/rtapi_shmem.c:506:4: warning: format ‘%d’ expects argument of
        type ‘int’, but argument 5 has type ‘size_t’ [-Wformat=]
	    rtapi_instance, sm.key, sm.size, retval);
	    ^
libnml:  silence -Wstrict-aliasing warnings (fat patch)

The business of e.g. `*((u_long *) temp_buffer + 2)`, where
`temp_buffer` is a character buffer, breaks strict aliasing rules:

    libnml/buffer/tcpmem.cc:1842:69: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]

The safe way to do this is make the buffer a union of a character
buffer and a uint32_t buffer.

No functions were used to manipulate these buffers (aside from the
'copy-and-paste' function), so this is a pretty massive change.
Makefile.inc:  Remove `-D_FORTIFY_SOURCE=0`

Many distros now enable `-D_FORTIFY_SOURCE=2` by default now (Ubuntu,
Fedora, Red Hat).

There was a problem with this in Xenomai 2.6.2.1, resolved in 2.6.3.

I hereby proclaim `-D_FORTIFY_SOURCE=0` unnecessary, and remove it
from build flags.

    <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
	[enabled by default]
    .../hal/classicladder/symbols.c:1:0: note: this is the location
	of the previous definition
syslog_async.c:  silence -Wunused-but-set-variable warning

No-op test of result to shut up compiler

    machinetalk/lib/syslog_async.c: In function ‘log_write_async’:
    machinetalk/lib/syslog_async.c:169:7: warning: variable ‘res’ set
      but not used [-Wunused-but-set-variable]
	   int res;
	       ^
hal/lib/hal_group.c:  silence -Wunused-but-set-variable warning

Check result of `halpr_foreach_member` and return

    hal/lib/hal_group.c: In function ‘halpr_group_compile’:
    hal/lib/hal_group.c:697:9: warning: variable ‘result’ set but not
      used [-Wunused-but-set-variable]
	 int result;
	     ^
hal/utils/halrmt.c:  silence -Wunused-but-set-variable warnings

First hunk: Check return value of `write()` function, then do nothing
interesting with it; the preceding `//FIXME` comment still applies.
Repeat for all warnings.

    hal/utils/halrmt.c:475:8: note: each undeclared identifier is reported
      only once for each function it appears in
    hal/utils/halrmt.c:470:8: warning: variable ‘ret’ set but not used
      [-Wunused-but-set-variable]
	    int ret, len;
		^
hal/drivers/hal_vti.c:  silence -Wunused-but-set-variable warnings

Silence warning by incrementing `junk` varible.

    hal/drivers/hal_vti.c: In function ‘vti_dac_write’:
    hal/drivers/hal_vti.c:794:11: warning: variable ‘junk’ set but not
      used [-Wunused-but-set-variable]
	 short junk;
	       ^
hal/lib/hal_ring.c:  silence -Wmaybe-uninitialized warnings

Set variable at time of declaration.

    .../hal/lib/hal_ring.c: In function ‘hal_ring_delete’:
    .../hal/lib/hal_ring.c:224:16: warning: ‘shmid’ may be used uninitialized
      in this function [-Wmaybe-uninitialized]
	   hal_print_msg(RTAPI_MSG_ERR,
			^
emc/motion/{command,motion}.c:  silence -Wstrict-prototypes warnings

No `void` in empty function declaration arg list

  .../emc/motion/command.c:361:5: warning: function declaration
    isn’t a prototype [-Wstrict-prototypes]
	 int abort_and_switchback()
	     ^