opal_path_nfs: enable debugging output

Now that "make check" siphons off stdout/stderr to logfiles, it's ok
to have output by default from tests.  This test fails often enough
that it's useful to see the diagnostic output.
opal_stdint.h: fix GCC diagnostic pragma
Merge pull request #307 from elenash/master

these changes fix direct routed component under mpirun; oob tcp and oob ...
opal_path_nfs test: do not try to test filesystems that can not be stat'd
Fix one typo in opal_path_nfs.c
comment out alps select in cray_xe6 platform

This alps selection stuff in the platform file is no longer required.
Fix the hostfile parser so it correctly ignores binding directives that are just integers. Fix the create_dmns function so we don't hang if we can't get an error before creating the job map for an application.
Add missing header files
You can't have a variable of the same name as the function...
Sigh - readd missing headers
Get the direct routed component to work with both TCP and USOCK OOB components. We previously had setup the direct component so it would only support direct-launched applications. Thus, all routes went direct between processes. However, if the job had been launched by mpirun, this made no sense - what you wanted instead was to have each app proc talk directly to its daemon, but have the daemons all directly connect to each other.

So we need all the routing code for dealing with cross-job communications, lifelines, etc. The HNP will be directly connected to all daemons as they must callback at startup, and so we need to track those children correctly so we know when it is okay to terminate.

We still have to support direct launch, though, as this is the only component we can use in that scenario. So if the app doesn't have daemon URI info, then it must fall back to directly connecting to everything.