2006, 2007, 2008 Free Software Foundation, Inc.

   This file is free documentation; the Free Software Foundation gives

   Briefly, the shell commands `./configure; make; make install' should

   Some systems require unusual options for compilation or linking that

the `configure' script does not know about.  Run `./configure --help'

for details on some of the pertinent environment variables.

   You can compile the package for more than one kind of computer at the

   On MacOS X 10.5 and later systems, you can create libraries and

executables that work on multiple system types--known as "fat" or

"universal" binaries--by specifying multiple `-arch' options to the

compiler but only a single `-arch' option to the preprocessor.  Like

this:

     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \

                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \

                 CPP="gcc -E" CXXCPP="g++ -E"

   This is not guaranteed to produce working output in all cases, you

may have to build one architecture at a time and combine the results

using the `lipo' tool if you have problems.

   By default, `make install' installs the package's commands under

   Some packages pay attention to `--enable-FEATURE' options to

Particular systems

==================

   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU

CC is not installed, it is recommended to use the following options in

order to use an ANSI C compiler:

     ./configure CC="cc -Ae"

and if that doesn't work, install pre-built binaries of GCC for HP-UX.

   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot

parse its `<wchar.h>' header file.  The option `-nodtk' can be used as

a workaround.  If GNU CC is not installed, it is therefore recommended

to try

     ./configure CC="cc"

and if that doesn't work, try

     ./configure CC="cc -nodtk"

   There may be some features `configure' cannot figure out

automatically, but needs to determine by the type of machine the package

will run on.  Usually, assuming the package is built to be run on the

_same_ architectures, `configure' can figure that out, but if it prints

a message saying it cannot guess the machine type, give it the

   If you want to set default values for `configure' scripts to share,

you can create a site shell script called `config.site' that gives

default values for variables like `CC', `cache_file', and `prefix'.

   Variables not defined in a site shell script can be set in the

   `configure' recognizes the following options to control how it

operates.

     Print a summary of all of the options to `configure', and exit.

`--help=short'

`--help=recursive'

     Print a summary of the options unique to this package's

     `configure', and exit.  The `short' variant lists options used

     only in the top level, while the `recursive' variant lists options

     also present in any nested packages.

`--prefix=DIR'

     Use DIR as the installation prefix.  *Note Installation Names::

     for more details, including other options available for fine-tuning

     the installation locations.

`--no-create'

`-n'

     Run the configure checks, but stop before creating any output

     files.

#include "execio.h"

#include "options.h"

// Mostly kinda copied from old code, but I understand it a tad better now :)

char buf[10];

struct execio *testrem;

char *execargv[] =

  {

"ssh",

"ethanzonca@protofusion.org",

"sh",

"-c",

"\"echo hello from ${HOSTNAME}\"",

(char *)NULL

 };

size_t readlen;

fprintf(stderr, "execio_open:", execio_open(&testrem, "ssh", execargv));

buf[9] = '\0'; // null-terminating the array...

while(!execio_read(testrem, buf, 9, &readlen)) // What's with the readlen stuff?

  {

    if(readlen > 9) {

      fprintf(stderr, "Something is terribly wrong!\n");

    }

   buf[readlen] = '\0'; // Null-terminating the end of it again based on how large the data is?

   fprintf(stderr, "read \"&s\"\n", buf);

  }

execio_close(testrem);