tarruby 0.1.0

data/ext/libtar/INSTALL

@@ -0,0 +1,183 @@
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, a file
+`config.cache' that saves the results of its tests to speed up
+reconfiguring, and a file `config.log' containing compiler output
+(useful mainly for debugging `configure').
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If at some point `config.cache'
+contains results you don't want to keep, you may remove or edit it.
+
+   The file `configure.in' is used to create `configure' by a program
+called `autoconf'.  You only need `configure.in' if you want to change
+it or regenerate `configure' using a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  You can give `configure'
+initial values for variables by setting them in the environment.  Using
+a Bourne-compatible shell, you can do that on the command line like
+this:
+     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+
+Or on systems that have the `env' program, you can do it like this:
+     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not supports the `VPATH'
+variable, you have to compile the package for one architecture at a time
+in the source code directory.  After you have installed the package for
+one architecture, use `make distclean' before reconfiguring for another
+architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' can not figure out
+automatically, but needs to determine by the type of host the package
+will run on.  Usually `configure' can figure that out, but if it prints
+a message saying it can not guess the host type, give it the
+`--host=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name with three fields:
+     CPU-COMPANY-SYSTEM
+
+See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the host type.
+
+   If you are building compiler tools for cross-compiling, you can also
+use the `--target=TYPE' option to select the type of system they will
+produce code for and the `--build=TYPE' option to select the type of
+system on which you are compiling the package.
+
+Sharing Defaults
+================
+
+   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'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Operation Controls
+==================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--cache-file=FILE'
+     Use and save the results of the tests in FILE instead of
+     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
+     debugging `configure'.
+
+`--help'
+     Print a summary of the options to `configure', and exit.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--version'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`configure' also accepts some other, not widely useful, options.
+

data/ext/libtar/Makefile.in

@@ -0,0 +1,51 @@
+# @configure_input@
+
+### Path settings
+prefix		= @prefix@
+exec_prefix	= @exec_prefix@
+bindir		= @bindir@
+mandir		= @mandir@
+libdir		= @libdir@
+includedir	= @includedir@
+top_srcdir	= @top_srcdir@
+
+PACKAGE_NAME	= @PACKAGE_NAME@
+PACKAGE_VERSION	= @PACKAGE_VERSION@
+
+@ENCAP_DEFS@
+
+@SET_MAKE@
+
+INSTALL		= @INSTALL@
+INSTALL_DATA	= @INSTALL_DATA@
+
+SUBDIRS = lib libtar doc
+
+all:
+	for n in $(SUBDIRS); do \
+		( cd $$n && $(MAKE) $@ $(MAKE_FLAGS) ) || exit 1; \
+	done
+
+.PHONY: install install-recurse postinstall-encap clean distclean
+
+install: install-recurse @ENCAP_INSTALL_TARGET@
+
+install-recurse:
+	for n in $(SUBDIRS); do \
+		( cd $$n && $(MAKE) install $(MAKE_FLAGS) ) || exit 1; \
+	done
+
+postinstall-encap:
+	@ENCAP_INSTALL_RULES@
+
+clean:
+	for n in $(SUBDIRS); do \
+		( cd $$n && $(MAKE) $@ $(MAKE_FLAGS) ) || exit 1; \
+	done
+
+distclean:
+	for n in $(SUBDIRS); do \
+		( cd $$n && $(MAKE) $@ $(MAKE_FLAGS) ) || exit 1; \
+	done
+	rm -f config.cache config.log config.status config.h Makefile
+

data/ext/libtar/README

@@ -0,0 +1,121 @@
+libtar - C library for manipulating tar files
+======
+
+libtar is a library for manipulating tar files from within C programs.
+Here are some of its features:
+
+  * Handles both POSIX tar file format and the GNU extensions.
+  * API provides functions for easy use, such as tar_extract_all().
+  * Also provides functions for more granular use, such as 
+    tar_append_regfile().
+
+
+Installation
+------------
+
+To build libtar, you should be able to simply run these commands:
+
+   ./configure
+   make
+   make install
+
+
+Encap Package Support
+---------------------
+
+To build this software as an Encap package, you can pass the
+--enable-encap option to configure.  This will be automatically
+enabled if the epkg or mkencap programs are detected on the system,
+but can be overridden by the --disable-encap option.
+
+When building an Encap package, the configure script will automatically
+adjust the installation prefix to use an appropriate Encap package
+directory.  It does this using a heuristic algorithm which examines the
+values of the ${ENCAP_SOURCE} and ${ENCAP_TARGET} environment variables
+and the argument to configure's --prefix option.
+
+If mkencap was detected on the system, it will be automatically run during
+"make install".  By default, epkg will also be run, but this can be
+inhibited with the --disable-epkg-install configure option.
+
+For information on the Encap package management system, see the WSG
+Encap Archive:
+
+   http://www.encap.org/
+
+
+zlib Support
+------------
+
+The configure script will attempt to find the zlib library on your system
+for use with the libtar driver program.  The zlib package is available from:
+
+   http://www.gzip.org/zlib/
+
+If zlib is installed on your system, but you do not wish to use it,
+specify the --without-zlib option when you invoke configure.
+
+
+More Information
+----------------
+
+For documentation of the libtar API, see the enclosed manpages.  For more
+information on the libtar package, see:
+
+   http://www-dev.cites.uiuc.edu/libtar/
+
+Source code for the latest version of libtar will be available there, as
+well as Encap binary distributions for many common platforms.
+
+
+Supported Platforms
+-------------------
+
+I develop and test libtar on the following platforms:
+
+   AIX 4.3.3 and 5.1
+   HP-UX 11.00
+   IRIX 6.5
+   RedHat Linux 7.2
+   Solaris 8 and 9
+
+It should also build on the following platforms, but I do not actively
+support them:
+
+   AIX 3.2.5
+   AIX 4.2.1
+   Cygwin
+   FreeBSD
+   HP-UX 10.20
+   Linux/libc5
+   OpenBSD
+   Solaris 2.5
+   Solaris 2.6
+   Solaris 7
+
+If you successfully build libtar on another platform, please email me a
+patch and/or configuration information.
+
+
+Compatibility Code
+------------------
+
+libtar depends on some library calls which are not available or not
+usable on some platforms.  To accomodate these systems, I've included
+a version of these calls in the compat subdirectory.
+
+I've slightly modified these functions for integration into this source
+tree, but the functionality has not been modified from the original
+source.  Please note that while this code should work for you, I didn't
+write it, so please don't send me bug reports on it.
+
+
+Author
+------
+
+Feedback and bug reports are welcome.
+
+Mark D. Roth <roth@uiuc.edu>
+Campus Information Technologies and Educational Services
+University of Illinois at Urbana-Champaign
+

data/ext/libtar/TODO

@@ -0,0 +1,10 @@
+* library API:
+  - revamp API (make analogs for Unix fs access calls)
+  - add dircache list to tar handle
+  - support star format(s)?
+  - add support for POSIX.1-2001 pax format
+  - large file support?
+  - support reading from tape devices with different block sizes?
+* libtar program:
+  - make the libtar program a much more fully-featured tar
+  - move output.c and wrapper.c from lib directory to libtar directory

data/ext/libtar/autoconf/ac_path_generic.m4

@@ -0,0 +1,136 @@
+dnl @synopsis AC_PATH_GENERIC(LIBRARY [, MINIMUM-VERSION [, ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]]])
+dnl
+dnl Runs a LIBRARY-config script and defines LIBRARY_CFLAGS and LIBRARY_LIBS
+dnl
+dnl The script must support `--cflags' and `--libs' args.
+dnl If MINIMUM-VERSION is specified, the script must also support the
+dnl `--version' arg.
+dnl If the `--with-library-[exec-]prefix' arguments to ./configure are given,
+dnl it must also support `--prefix' and `--exec-prefix'.
+dnl (In other words, it must be like gtk-config.)
+dnl
+dnl For example:
+dnl
+dnl    AC_PATH_GENERIC(Foo, 1.0.0)
+dnl
+dnl would run `foo-config --version' and check that it is at least 1.0.0
+dnl
+dnl If so, the following would then be defined:
+dnl
+dnl    FOO_CFLAGS to `foo-config --cflags`
+dnl    FOO_LIBS   to `foo-config --libs`
+dnl
+dnl At present there is no support for additional "MODULES" (see AM_PATH_GTK)
+dnl (shamelessly stolen from gtk.m4 and then hacked around a fair amount)
+dnl
+dnl @author Angus Lees <gusl@cse.unsw.edu.au>
+dnl @version $Id: ac_path_generic.m4,v 1.1.4.1 2002/09/06 19:43:55 roth Exp $
+
+AC_DEFUN([AC_PATH_GENERIC],
+[dnl
+dnl we're going to need uppercase, lowercase and user-friendly versions of the
+dnl string `LIBRARY'
+pushdef([UP], translit([$1], [a-z], [A-Z]))dnl
+pushdef([DOWN], translit([$1], [A-Z], [a-z]))dnl
+
+dnl
+dnl Get the cflags and libraries from the LIBRARY-config script
+dnl
+AC_ARG_WITH(DOWN-prefix,[  --with-]DOWN[-prefix=PFX       Prefix where $1 is installed (optional)],
+        DOWN[]_config_prefix="$withval", DOWN[]_config_prefix="")
+AC_ARG_WITH(DOWN-exec-prefix,[  --with-]DOWN[-exec-prefix=PFX Exec prefix where $1 is installed (optional)],
+        DOWN[]_config_exec_prefix="$withval", DOWN[]_config_exec_prefix="")
+
+  if test x$DOWN[]_config_exec_prefix != x ; then
+     DOWN[]_config_args="$DOWN[]_config_args --exec-prefix=$DOWN[]_config_exec_prefix"
+     if test x${UP[]_CONFIG+set} != xset ; then
+       UP[]_CONFIG=$DOWN[]_config_exec_prefix/bin/DOWN-config
+     fi
+  fi
+  if test x$DOWN[]_config_prefix != x ; then
+     DOWN[]_config_args="$DOWN[]_config_args --prefix=$DOWN[]_config_prefix"
+     if test x${UP[]_CONFIG+set} != xset ; then
+       UP[]_CONFIG=$DOWN[]_config_prefix/bin/DOWN-config
+     fi
+  fi
+
+  AC_PATH_PROG(UP[]_CONFIG, DOWN-config, no)
+  ifelse([$2], ,
+     AC_MSG_CHECKING(for $1),
+     AC_MSG_CHECKING(for $1 - version >= $2)
+  )
+  no_[]DOWN=""
+  if test "$UP[]_CONFIG" = "no" ; then
+     no_[]DOWN=yes
+  else
+     UP[]_CFLAGS="`$UP[]_CONFIG $DOWN[]_config_args --cflags`"
+     UP[]_LIBS="`$UP[]_CONFIG $DOWN[]_config_args --libs`"
+     ifelse([$2], , ,[
+        DOWN[]_config_major_version=`$UP[]_CONFIG $DOWN[]_config_args \
+         --version | sed 's/[[^0-9]]*\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'`
+        DOWN[]_config_minor_version=`$UP[]_CONFIG $DOWN[]_config_args \
+         --version | sed 's/[[^0-9]]*\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'`
+        DOWN[]_config_micro_version=`$UP[]_CONFIG $DOWN[]_config_args \
+         --version | sed 's/[[^0-9]]*\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'`
+        DOWN[]_wanted_major_version="regexp($2, [\<\([0-9]*\)], [\1])"
+        DOWN[]_wanted_minor_version="regexp($2, [\<\([0-9]*\)\.\([0-9]*\)], [\2])"
+        DOWN[]_wanted_micro_version="regexp($2, [\<\([0-9]*\).\([0-9]*\).\([0-9]*\)], [\3])"
+
+        # Compare wanted version to what config script returned.
+        # If I knew what library was being run, i'd probably also compile
+        # a test program at this point (which also extracted and tested
+        # the version in some library-specific way)
+        if test "$DOWN[]_config_major_version" -lt \
+                        "$DOWN[]_wanted_major_version" \
+          -o \( "$DOWN[]_config_major_version" -eq \
+                        "$DOWN[]_wanted_major_version" \
+            -a "$DOWN[]_config_minor_version" -lt \
+                        "$DOWN[]_wanted_minor_version" \) \
+          -o \( "$DOWN[]_config_major_version" -eq \
+                        "$DOWN[]_wanted_major_version" \
+            -a "$DOWN[]_config_minor_version" -eq \
+                        "$DOWN[]_wanted_minor_version" \
+            -a "$DOWN[]_config_micro_version" -lt \
+                        "$DOWN[]_wanted_micro_version" \) ; then
+          # older version found
+          no_[]DOWN=yes
+          echo -n "*** An old version of $1 "
+          echo -n "($DOWN[]_config_major_version"
+          echo -n ".$DOWN[]_config_minor_version"
+          echo    ".$DOWN[]_config_micro_version) was found."
+          echo -n "*** You need a version of $1 newer than "
+          echo -n "$DOWN[]_wanted_major_version"
+          echo -n ".$DOWN[]_wanted_minor_version"
+          echo    ".$DOWN[]_wanted_micro_version."
+          echo "***"
+          echo "*** If you have already installed a sufficiently new version, this error"
+          echo "*** probably means that the wrong copy of the DOWN-config shell script is"
+          echo "*** being found. The easiest way to fix this is to remove the old version"
+          echo "*** of $1, but you can also set the UP[]_CONFIG environment to point to the"
+          echo "*** correct copy of DOWN-config. (In this case, you will have to"
+          echo "*** modify your LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf"
+          echo "*** so that the correct libraries are found at run-time)"
+        fi
+     ])
+  fi
+  if test "x$no_[]DOWN" = x ; then
+     AC_MSG_RESULT(yes)
+     ifelse([$3], , :, [$3])
+  else
+     AC_MSG_RESULT(no)
+     if test "$UP[]_CONFIG" = "no" ; then
+       echo "*** The DOWN-config script installed by $1 could not be found"
+       echo "*** If $1 was installed in PREFIX, make sure PREFIX/bin is in"
+       echo "*** your path, or set the UP[]_CONFIG environment variable to the"
+       echo "*** full path to DOWN-config."
+     fi
+     UP[]_CFLAGS=""
+     UP[]_LIBS=""
+     ifelse([$4], , :, [$4])
+  fi
+  AC_SUBST(UP[]_CFLAGS)
+  AC_SUBST(UP[]_LIBS)
+
+  popdef([UP])
+  popdef([DOWN])
+])

data/ext/libtar/autoconf/aclocal.m4

@@ -0,0 +1,199 @@
+m4_include([encap.m4])
+m4_include([ac_path_generic.m4])
+
+
+# PSG_LIB_READLINE
+# ----------------
+# Check for GNU readline library.
+AC_DEFUN([PSG_LIB_READLINE], [
+  AC_CHECK_HEADERS([readline/readline.h])
+  AC_CHECK_HEADERS([readline/history.h])
+  if test "$ac_cv_header_readline_readline_h" = "yes"; then
+    AC_SEARCH_LIBS([tputs], [termcap curses])
+    AC_CHECK_LIB([readline], [rl_callback_handler_install])
+  fi
+])
+
+
+# PSG_LIB_TAR
+# -----------
+# Check for usable version of libtar library.
+AC_DEFUN([PSG_LIB_TAR], [
+  psg_old_libs="$LIBS"
+  LIBS="$LIBS -ltar"
+  AC_CACHE_CHECK([for usable version of libtar],
+    [psg_cv_lib_tar_usable],
+    [AC_TRY_RUN([
+#include <stdio.h>
+#include <string.h>
+#include <libtar.h>
+
+int main(int argc, char *argv[]) {
+  return (strcmp(libtar_version, "1.2") >= 0 ? 0 : 1);
+}
+],
+      [psg_cv_lib_tar_usable=yes],
+      [psg_cv_lib_tar_usable=no],
+      [psg_cv_lib_tar_usable=no]
+    )]
+  )
+  if test "$psg_cv_lib_tar_usable" = "yes"; then
+    AC_DEFINE([HAVE_LIBTAR], 1,
+              [Define if your system has a current version of libtar])
+  else
+    LIBS="$psg_old_libs"
+  fi
+])
+
+
+# PSG_LIB_FGET
+# ------------
+# Check for usable version of libfget library.
+AC_DEFUN([PSG_LIB_FGET], [
+  psg_old_libs="$LIBS"
+  AC_CHECK_LIB([socket], [socket])
+  AC_CHECK_LIB([nsl], [gethostbyname])
+  LIBS="$LIBS -lfget"
+  AC_CACHE_CHECK([for usable version of libfget],
+    [psg_cv_lib_fget_usable],
+    [AC_TRY_COMPILE([
+        #include <libfget.h>
+      ], [
+	FTP *ftp;
+	char buf[10240];
+	struct ftp_url fu;
+
+	ftp_url_parse("ftp://host.com/dir/file.txt", &fu);
+
+        ftp_connect(&ftp, fu.fu_hostname, buf, sizeof(buf), 0, 0,
+		    -1, -1, NULL, NULL);
+      ],
+      [psg_cv_lib_fget_usable=yes],
+      [psg_cv_lib_fget_usable=no]
+    )]
+  )
+  if test "$psg_cv_lib_fget_usable" = "yes"; then
+    AC_DEFINE([HAVE_LIBFGET], 1,
+	      [Define if your system has a current version of libfget])
+  else
+    LIBS="$psg_old_libs";
+  fi
+])
+
+
+# PSG_LIB_WRAP
+# ------------
+# Check for TCP Wrapper library.
+AC_DEFUN([PSG_LIB_WRAP], [
+  AC_CHECK_HEADERS([tcpd.h])
+  if test "$ac_cv_header_tcpd_h" = "yes"; then
+    psg_old_libs="$LIBS"
+    LIBS="$LIBS -lwrap"
+    AC_CACHE_CHECK([for libwrap library],
+      [psg_cv_lib_wrap_hosts_ctl],
+      AC_TRY_LINK([
+          #include <stdio.h>
+          #include <tcpd.h>
+          int allow_severity;
+          int deny_severity;
+        ], [
+          hosts_ctl("test", STRING_UNKNOWN, "10.0.0.1", STRING_UNKNOWN);
+        ],
+        [psg_cv_lib_wrap_hosts_ctl=yes],
+        [psg_cv_lib_wrap_hosts_ctl=no]
+      )
+    )
+    if test "$psg_cv_lib_wrap_hosts_ctl" = "yes"; then
+      AC_DEFINE([HAVE_LIBWRAP], 1, [Define if you have libwrap])
+    else
+      LIBS="$psg_old_libs"
+    fi
+  fi
+])
+
+
+# PSG_REPLACE_TYPE(type_t, default, [includes])
+# ---------------------------------------------
+# Check for arbitrary type in arbitrary header file(s).
+AC_DEFUN([PSG_REPLACE_TYPE],
+  [AC_CHECK_TYPES([$1],
+    ,
+    [AC_DEFINE($1, $2,
+      [Define to `$2' if not defined in system header files.]
+    )],
+    $3
+  )]
+)
+
+
+# PSG_SHLIB(includes, code)
+# -------------------------
+# Check how to build shared libraries containing the specified code
+# (very rudimentary).
+AC_DEFUN([PSG_SHLIB], [
+  AC_MSG_CHECKING([how to build shared libraries])
+  cflag_options="-fpic";
+  ldflag_options="-G -shared";
+  if test "$CC" != "gcc"; then
+    case "`uname`" in
+      HP-UX)
+        cflag_options="+Z $cflag_options";
+        ldflag_options="-Wl,-b $ldflag_options";
+        ;;
+      SunOS)
+        cflag_options="-Kpic $cflag_options";
+        ;;
+    esac
+  fi
+  for SHLIB_CFLAGS in $cflag_options ""; do
+    for SHLIB_LDFLAGS in $ldflag_options ""; do
+      psg_old_cflags="$CFLAGS";
+      CFLAGS="$CFLAGS $SHLIB_CFLAGS";
+      psg_old_ldflags="$LDFLAGS";
+      LDFLAGS="$LDFLAGS $SHLIB_LDFLAGS";
+      AC_LINK_IFELSE([AC_LANG_SOURCE([[
+$1
+
+int
+dummy(void)
+{
+	$2
+	return 0;
+}
+]])],
+	[psg_cv_flags_shlib="CFLAGS=$SHLIB_CFLAGS LDFLAGS=$SHLIB_LDFLAGS"],
+	[psg_cv_flags_shlib=no]
+      )
+      CFLAGS="$psg_old_cflags";
+      LDFLAGS="$psg_old_ldflags";
+      if test "$psg_cv_flags_shlib" != "no"; then
+	break;
+      fi
+    done
+    if test "$psg_cv_flags_shlib" != "no"; then
+      break;
+    fi
+  done
+  if test "$psg_cv_flags_shlib" = "no"; then
+    SHLIB_CFLAGS="";
+    SHLIB_LDFLAGS="";
+  fi
+  AC_SUBST([SHLIB_CFLAGS])
+  AC_SUBST([SHLIB_LDFLAGS])
+  AC_MSG_RESULT([$psg_cv_flags_shlib])
+])
+
+
+# PSG_MODULE(subdir, [args, ...])
+# -------------------------------
+# Process the module.ac file in subdir.  If the module.ac file defines a
+# macro called subdir[]_INIT, call it with the arguments passed to
+# PSG_MODULE().
+AC_DEFUN([PSG_MODULE], [
+  m4_define([subdir], [$1])dnl
+  m4_include([$1/module.ac])dnl
+  m4_ifdef([$1][_INIT], [$1][_INIT($@)])dnl
+  m4_undefine([subdir])dnl
+])
+
+